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 |