Re: [Ipmitool-devel] Migration to GitHub

[Al C. <ch...@ll...>]

> Anyway, I wasn't planning to shut down the mailing lists as it is a
> good
> means of communication on common topics like this. The idea was to
> move
> source code and bug tracking to github, leaving it integrated with
> sourceforge so that users would still be able to find the project the
> usual way, take releases from sourceforge if they prefer, and use
> mailing lists if they want to. I just want to make development
> easier.

Just a comment.  I assumed "Migrate to Github" meant "everything gets
moved" kind of thing.  I think having two locations be "valid" is
confusing.

One idea, which is what I did for FreeIPMI, is I made a mirror of the
repo on github for my own personal development.  I clearly indicate its
a mirror, indicate I am the maintainer and willing to accept pull
requests, but the main stuff is elsewhere.

Al


On Fri, 2018-04-06 at 16:06 +0300, Alexander Amelkin wrote:
> 06.04.2018 12:49, Vasant Hegde wrote:
> > On 04/04/2018 03:09 PM, Alexander Amelkin wrote:
> > > Hello everybody!
> > > 
> > > As I've started administering ipmitool project recently, I've
> > > noticed
> > > that SourceForge is extremely inconvenient in terms of code
> > > review, and,
> > > what is more important, unstable. I encounter extremely slow git
> > > operations, now and then I see in browser that "repository
> > > metadata is
> > > not available", I've seen server errors when accessing pull
> > > requests,
> > > and so on.
> > > 
> > > I start thinking about migrating the project to GitHub that is
> > > much more
> > > stable and provides better development and code reviewing tools.
> > > However
> > > I may be missing something about convenience of SourceForge for
> > > users,
> > > so I would like to hear any opinions against migration in general
> > > or
> > > against GitHub in particular.
> > 
> > Good move.
> > 
> > AFAIK github doesn't provide mailing list facility. So do you want
> > to
> > keep existing mailing list -OR- switch to pull request method for
> > submitting patches/questions?
> 
> Thanks for this point. Personally I think that mailing lists are an
> inconvenient outdated technology if used for patches and their
> discussion. I prefer bugtrackers (github issues, sourceforge tickets,
> whatever). Pull requests are good, but patches attached to issues are
> fine as well.
> 
> Anyway, I wasn't planning to shut down the mailing lists as it is a
> good
> means of communication on common topics like this. The idea was to
> move
> source code and bug tracking to github, leaving it integrated with
> sourceforge so that users would still be able to find the project the
> usual way, take releases from sourceforge if they prefer, and use
> mailing lists if they want to. I just want to make development
> easier.
> 
> With best regards,
> Alexander.
> 
> 
> -------------------------------------------------------------------
> -----------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Ipmitool-devel mailing list
> Ipm...@li...
> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel