All the teams I could find... and some issues

1

Ok, I put together a list of all the projects with teams that I could find…

http://www.binarychicken.com/teamhaiku/DistributedComputing.html

Some things to note:

I put any BeOS-related team I could find in there as well (for nostalgia if nothing else)… and I noticed that SETI@Home has an OpenBeOS team already. To top it off, it already has a lot of members and decent credit built-up.

I’m not sure what to do about this, but I have already emailed Andrew Edward McCall to see if he can think of anything. BOINC projects allow teams to be renamed - but I can’t see any way to merge them together :frowning:

It also occurred to me that we have the opportunity to rename some of the old Team BeOS teams if we want - allowing Team Haiku to build on their credit already obtained. This of course assumes that the team founders (and members?) would be OK with this. Ultimately it might be best to keep them separate so that those who wish to can continue supporting those teams.

If I missed any completed projects - or existing projects - please let me know so I can add them to this list. In due time, this list will be formally set up on the Team Haiku website with some other goodies if possible :slight_smile:

Update: Oh BTW, if anyone’s interested, I also created a #teamhaiku on freenode for those who want to discuss anything via IRC :slight_smile:

2

Good work here, Urias.

It would certainly be nice if we could merge the Haiku and BeOS teams together, provided everyone in those teams are cool with it; I would suspect not many would be against it.

3
j_freeman wrote:
It would certainly be nice if we could merge the Haiku and BeOS teams together, provided everyone in those teams are cool with it; I would suspect not many would be against it.

Yeah, I’m still struggling (internally) on this. There is a certain “legacy” that Team BeOS represents - and maybe we should retain it as-is for nostalgic purposes.

On the other hand, it would be nice to take advantage of all the hard work that has been done on those teams!

Maybe it’s best to continue our current path and start fresh as a statement of “a new beginning” and to show that support for Haiku is a truly renewed interest, and not just a bunch of people who USED to contribute when BeOS was still big.

There are some technical issues as well:

  1. Most projects now have a Team Haiku (I’ll admit this is partially my fault as I recently went on a team-creation crusade)

  2. Some of the team leaders could be difficult to contact, or even persuade.

  3. There doesn’t appear to be any way to “merge” teams on any project I’ve looked at. I suspect it would be considered “unfair” to most participants.