Daniel Povey <dpo...@gmail.com> writes: > Everyone, > > Since the Son of GridEngine maintainer, Dave Love, seems to be MIA,
It's conventional to be allowed a couple of weeks, and it can be difficult to read work email these days... I lost access to the repo at Liverpool due to not being able to work around unhelpful policy. I was interrupted moving stuff to Sourceforge by their infrastraucture troubles, and wasn't able to get back to it after that stabilized. (I'd like to have re-sited the Trac/Darcs instance, like SF used to support, but don't feel like paying for hosting myself.) Anyhow, you can see fixes for recent distributions in the rpm repository, and I'm trying to prepare a new release, despite the general lack of incentive. It's partly hamstrung by not being able to test properly these days. I'll try to sort out pushing to a new repo soon, but it requires non-trivial reconciling of darcs and git/mercurial branches. I'll also attempt to sort something out at Liverpool -- at least re-directing mail. > I > have initiated a discussion on the gridengine-users mailing list here > http://gridengine.org/pipermail/users/2018-May/thread.html > about creating a project on GitHub that will take up the torch from > the current team. I'd have expected something initially on the project list. (There has never been a team, unfortunately, but thanks, Mark, in particular.) > Search for 'Son of GridEngine succession'. There > is some discussion about the name there, and at the bottom of the > thread you'll find a reference to a Doodle poll for what the project > should be called. > > I thought I should post about it on this list as well, in case there > is anyone involved in the maintenance of Son of GridEngine who is on > that list but not on the gridengine-users list. Also I wonder if > anyone could weigh in on whether people in the original Son of > GridEngine team would get upset if we used the same name "Son of > GridEngine"-- since that is the name choice that seems to be leading > in the poll right now. It's free software with not trademark, but I'm afraid it will be confusing in the short term to have multiple versions of the source and other artefacts in different places. (The name was carefully chosen in the hacker spirit when Oracle's proprietary interest was unclear.) I'm not clear what the provenance of https://github.com/son-of-gridengine/sge is, and why it apparently wasn't just pulled from the git mirror at Liverpool. The main branch contains patches that won't be in the planned release -- I think at lest one is broken, and others caused problems I hadn't resolved. There are actually clashes between patches in the development and release branches, as alluded to above. I'm happy for someone to take over maintenance (to the extent it's relevant these days, which seems to be not much). However, I'd like it done properly cleanly, specifically maintaining everything like the issue history, and other source and documentation. (There's actually some stuff, like a version of closed issues from sunsource and the pre-version 6 source, that I never did put up.) I worry that people don't appreciate the need for history that becomes apparent during maintenance, especially with a horrible code base. I can probably at least provide some guidance that looks as if it would have been helpful, looking at issues on that repository. _______________________________________________ SGE-discuss mailing list SGE-discuss@liv.ac.uk https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
