From: Jean-Baptiste <jea...@gm...> - 2011-05-30 19:01:47
|
Hello everybody, correct me if i'm wrong, but it seems that the current repository is located on sourceforge: http://sourceforge.net/projects/moosefs/develop. I saw an unofficial github mirror (https://github.com/icy/moosefs). Is there any chance for it to become the official one ? Github offers a greater flexibility for external contribution than sourceforge, i think everybody agree on that. By the way, is there a reason why there is no activity on the repository since the last release ? Maybe are you working on a private repository ? I think it could be nice to see the current work on your current moosefs branch and motivate people to contribute ! Anyway, thank you for sharing moosefs with the world. Regards, Jean-Baptiste |
From: Anh K. H. <ky...@vi...> - 2011-05-31 14:14:09
|
On Mon, 30 May 2011 19:01:41 +0000 Jean-Baptiste <jea...@gm...> wrote: > correct me if i'm wrong, but it seems that the current repository is > located on sourceforge: > http://sourceforge.net/projects/moosefs/develop. I saw an unofficial > github mirror (https://github.com/icy/moosefs). Actually this is my fork (for my personal patches). The mirror has moved to new address https://github.com/xmirror/moosefs > Is there any chance for it to become the official one ? Github > offers a greater flexibility for external contribution than > sourceforge, i think everybody agree on that. I agree with you that using Git will help MooseFS to get more contributors. I am going to write some scripts, to make repositories at "xmirror" up-to-date. Surely it's nice if there is any official mirror on Github. > By the way, is there a reason why there is no activity on the > repository since the last release ? Maybe are you working on a > private repository ? I think it could be nice to see the current > work on your current moosefs branch and motivate people to > contribute ! IMHO, Git allows developers to work *easily* on private branches, so we may not see any activities on the repository. BTW, this is my opinion; this isn't official reply from MooseFS team. Regards, -- Anh Ky Huynh @ ICT Registered Linux User #392115 |
From: Jean-Baptiste <jb...@jb...> - 2011-06-04 15:20:20
|
On Tue, May 31, 2011 at 2:13 PM, Anh K. Huynh <ky...@vi...> wrote: > IMHO, Git allows developers to work *easily* on private branches, so we may not see any activities on the repository. BTW, this is my opinion; this isn't official reply from MooseFS team. Thank you for your answer. Is that possible to have an official reply from the MooseFS about those private branches ? It could be quite frustrating to develop something on the public trunk and having a difficult merge time when a new release pops in the public git repository. I'm not saying anything wrong about the MooseFS team here, i think it's perfectly understandable to have non-public working repository, but maybe it will encourage people to contribute if they can have an eye on the work in progress =) Jean-Baptiste |
From: Anh K. H. <ky...@vi...> - 2011-06-05 02:49:03
|
On Sat, 4 Jun 2011 15:05:50 +0000 Jean-Baptiste <jb...@jb...> wrote: > On Tue, May 31, 2011 at 2:13 PM, Anh K. Huynh <ky...@vi...> > wrote: > > > IMHO, Git allows developers to work *easily* on private branches, > > so we may not see any activities on the repository. BTW, this is > > my opinion; this isn't official reply from MooseFS team. > > Thank you for your answer. Is that possible to have an official > reply from the MooseFS about those private branches ? It could be > quite frustrating to develop something on the public trunk and > having a difficult merge time when a new release pops in the public > git repository. > > I'm not saying anything wrong about the MooseFS team here, i think > it's perfectly understandable to have non-public working repository, > but maybe it will encourage people to contribute if they can have an > eye on the work in progress =) I think the best way is... to do something, don't wait. The source is open and any one can benefit from that, and any developers play with it, or they have to wait for the authors. Some months ago I started with very tiny things: add comments to MooseFS code, thinking that comments may help someone. Unfortunately, I permanently deleted my works when cleaning up my computer and my git repositories :( Now I focus on the Python script "mfscgi" which is used to monitor the MooseFS. I think I would rewrite it in a more flexible way, so that the notification system can use it directly. Please wait for my commit :P Or join me ! Just my two cents, -- Anh Ky Huynh @ ICT Registered Linux User #392115 |
From: Anh K. H. <ky...@vi...> - 2011-06-05 03:04:02
|
On Sat, 4 Jun 2011 15:05:50 +0000 Jean-Baptiste <jb...@jb...> wrote: > On Tue, May 31, 2011 at 2:13 PM, Anh K. Huynh <ky...@vi...> > wrote: > > > IMHO, Git allows developers to work *easily* on private branches, > > so we may not see any activities on the repository. BTW, this is > > my opinion; this isn't official reply from MooseFS team. > > Thank you for your answer. Is that possible to have an official > reply from the MooseFS about those private branches ? It could be > quite frustrating to develop something on the public trunk and > having a difficult merge time when a new release pops in the public > git repository. > > I'm not saying anything wrong about the MooseFS team here, i think > it's perfectly understandable to have non-public working repository, > but maybe it will encourage people to contribute if they can have an > eye on the work in progress =) BTW, the IRC channel #moosefs is quite active and open as I know. Feel to join it :) I love the guys there! -- Anh Ky Huynh @ ICT Registered Linux User #392115 |
From: Michal B. <mic...@ge...> - 2011-06-06 08:30:08
|
Hi! Let me speak about the git repositories and the code maintenance. The only official git repository is hosted at SourceForge.net. Although MooseFS is open source we feel highly responsible for its stability and quality - we make extensive tests in our development and production environments and only after that we release a new version. Your contributions are more than welcome but we prefer to get them in the form of patches which we can easily analyze and test. Usually a patch contributed by open community is "finetuned" by our team and gets published in the next release. Unfortunately when everybody started to commit to their branches requesting us to test, merge, publish, etc., it would take from us lots of energy and we would have less time for developing the code. So please understand our point of view where the stability is our main goal. Kind regards Michał Borychowski MooseFS Support Manager _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gemius S.A. ul. Wołoska 7, 02-672 Warszawa Budynek MARS, klatka D Tel.: +4822 874-41-00 Fax : +4822 874-41-01 -----Original Message----- From: Anh K. Huynh [mailto:ky...@vi...] Sent: Sunday, June 05, 2011 3:18 AM To: Jean-Baptiste Cc: moo...@li... Subject: Re: [Moosefs-users] git source code repository On Sat, 4 Jun 2011 15:05:50 +0000 Jean-Baptiste <jb...@jb...> wrote: > On Tue, May 31, 2011 at 2:13 PM, Anh K. Huynh <ky...@vi...> > wrote: > > > IMHO, Git allows developers to work *easily* on private branches, > > so we may not see any activities on the repository. BTW, this is > > my opinion; this isn't official reply from MooseFS team. > > Thank you for your answer. Is that possible to have an official > reply from the MooseFS about those private branches ? It could be > quite frustrating to develop something on the public trunk and > having a difficult merge time when a new release pops in the public > git repository. > > I'm not saying anything wrong about the MooseFS team here, i think > it's perfectly understandable to have non-public working repository, > but maybe it will encourage people to contribute if they can have an > eye on the work in progress =) BTW, the IRC channel #moosefs is quite active and open as I know. Feel to join it :) I love the guys there! -- Anh Ky Huynh @ ICT Registered Linux User #392115 ---------------------------------------------------------------------------- -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
From: Jean-Baptiste <jb...@jb...> - 2011-06-06 09:59:09
|
2011/6/6 Michal Borychowski <mic...@ge...>: > Unfortunately when everybody started to commit to their branches requesting > us to test, merge, publish, etc., it would take from us lots of energy and > we would have less time for developing the code. So please understand our > point of view where the stability is our main goal. I respect that. Thank your for your official answer. |