From the sound of it we have the source code already preserved. It
would be worth seeing if we can get a snapshot of the wiki, forums and
any other documentation as well. Is there anything else we need?
From my point of view the best place for a new subversion would be
google code as that's where our open source projects are hosted. I'm
not familliar with github - what do they provide?
I know what you mean about google restricting licenses but TBH I agree
with them that the proliferation of open source licenses is not a good
thing. That's extremely off topic though! It does remind me though
that licensing in general is a potential problem now since we may lose
the option Sun were providing to get a commercial license for those
people who need/want it.
TBH as I see it at the moment we have the following things that need
doing:
1. Preserve as much data as possible from the existing PDS sites
against whenever they shutdown.
2. Evaluate the current known bugs and the state of development on
multi-node.
3. Establish just what development work still needs doing and who is
available to do it.
Anyone got anything to add to that?
Just one thing: you are happy with SVN because you don't know git!
Trust me! I've been there before :)
Barring that, copy/paste works.
Rich
--
Sent from my mobile device
Rich Elswick
Also kudos to the Red Dwarf fork name....very clever
Cheers!
-John
Anyways, I'm studying a BSc in Computer Science, and was going to use
Darkstar and Slipstream as a basis for my dissertation project next
year, and to be quite honest this news has gotten me a little upset,
but finding this group made me think that my dissertation project was
still possible.
I have access to a very good (and very experienced, he must be in his
late 60's) programming lecturer. I've explained Darkstar to him, and
he seems interested enough to guide me in my exploits, but the
question now is what do I base my study on?
I'm going to have time dedicated to this as part of my study time, and
I wonder if I could take on a little portion of the research we need
to do to get multinode?
I'm offering any help I can, and it'd be a great dissertation piece,
considering the complexity of the issue, and the ground-breaking
nature of Darkstar.
Do we have the conclusions Sun came to at the point of rejection of
the project? Jeff do you think there's a possibility Sun would pass
over all research documentation to this project as well, or are we on
our own in that department?
What I'm a little concerned about is that Sun have tested all the
multi-node work, it hasn't worked out, and the project has been
dropped as a result. I'd really like to know if that is the situation,
because there's no use flogging a dead horse, but there could be good
elements we can re-use.
This is based on absolutely no inside knowledge and I doubt anyone who
has access to such knowledge can comment in a public forum like this
but I'm pretty sure that with the Oracle takeover someone has gone
through every project in Sun and asked awkward questions like "where
is the revenue stream, how is this going to make us money". The answer
to that is always pretty vague when it comes to both an open source
project (unless you have a reasonably sized user base of people
actively paying for support contracts) and a research project. That
means that an open source research project is doubly at risk and this
eventuality has been a real possibility from the moment the takeover
was announced.
I was really hoping they would get multi node finished before the axe
fell though as that is the thing that needs a focussed and dedicated
effort. Ongoing maintanence and bugfix is a lot easier to keep
rolling.
On Feb 3, 8:09 pm, nokama <willbith...@hotmail.com> wrote:
> What I'm a little concerned about is that Sun have tested all the
> multi-node work, it hasn't worked out, and the project has been
> dropped as a result. I'd really like to know if that is the situation,
> because there's no use flogging a dead horse, but there could be good
> elements we can re-use.
Have we got all the affinity grouping code in our branch? That seemed
to be a main key in it all, and it's something I'd really like to
study. Last I heard it was getting reviewed, but was in a completed
state, but I have had other things going on so haven't paid much
attention.
-M.
This project does need to be saved though, in a complete form it would
surpass by far anything that's available to the public for a
reasonable price, if not ultimately.
I'm sure you'll keep everyone informed as to what's going on when you
hear it.
On Feb 3, 10:32 pm, Jeffrey Kesselman <jef...@gmail.com> wrote:
> I think there is definitely that option... and I'm really happy to see
> the interest in staying together and doing what needs to be done with PDS.
>
> I understand from folks i know on the (ex) labs team that some of them are
> still very interested in trying to save the project themselves.
>
> I set this up as a safegaurd in case they fail, but as long as they are
> trying to make it coem together still I don't want to get too far ahead in
> terms of striking out on our own.
>
> That seem fair and reasonable to everyone?
>
Absolutely. The urgent need was to make sure that we had all the source
code and a communications link ready in case the old site disappeared
and that is now done. I'd be very glad to hear that some or all of the
PDS team are still working on the project though and if they are able to
do so then I agree we should try and support them rather than fracturing
the community.
Tim
-David
PDS was/is the winner in our selection process for a server
technology, and I am willing to help keep it that way.
Thanks for setting this up and keeping it going!
-- Josh
I would like to help too, I would be out of my depth (I think) if I
tried to help with the development of new/unfinished features, however
I will be glad to help with bug fixing, simple&boring code monkey work
or even (gulp) documenting...
Saludos.
Frodo.
I'm sad to see the project's sponsorship fall aside, but encouraged to
see so many speak up for it and join the group this fast. I cannot
contribute anything personally yet, aside from encouragement, and
you've got that. Remember the old axiom - any publicity is good
publicity - and try to use this event to recruit many more developers
for the project. A speedy re-launch will help take advantage of the
attention before it dies down. The faster you figure out the exact
fate of the official site, forums, code, etc, the better.
http://www.projectdarkstar.com/forum/?topic=1550.0;topicseen
It seems with luck that this list will become obsolete as fast as it was
formed - but still it served it's purpose as an emergency fall-back!
Tim