Turadg Aleahmad wrote: > I know Scott's paid a lot of attention to how other open-source > communities work, like Eclipse. Scott, could you add to that page a > sketch of how things would work if we adopted the Eclipse model? Or > any other existing model? I'll try to find some time to do that. Some of my ideas below come from learning about the Eclipse community.
> > Maybe this particular recent situation can help get us thinking: > members of the SAIL community developed a portal in Java and want to > share it with the rest of SAIL. While they are over half the > developers, key SAIL contributors are not involved in that portal. > How does it get named? Are their qualifications for being called > "SAIL <whatever>"? Do we have an incubation period? Is it too early > to introduce that formality? I've been using the term SAIL Portal to describe it. However it is a little confusing that there are other portals that launch the SAIL Runtime, and connect with the SDS. I think in general it might be better to use names that don't include SAIL, because there will always be another option. I think it might be more consistent to use the term SAIL X to describe a class of things. Then we could say things like: the TELS portal is a SAIL Portal the DIY plus CC PHP portal is a SAIL Portal the rails sds is a SAIL Data Service. the sail-core project provides a SAIL Content Model, a SAIL Learner Data Model, and a SAIL Application Framework. But we have this existing stuff like SAIL Data Service and now the SAIL Portal, which are instances of these things, and it hard to pull back names once they start getting used. Perhaps it isn't too late for the SAIL Portal, what do people think about renaming it? Lets look at the SAIL Content Model provided by sail-core as an example. This content model uses Pods and Beans inside of a Curnit to store the content of project. At the time we all created it together and we were all using it for TELS. So it made perfect sense to put it in a project called sail-core. Now it is one of two options for storing the content of a project. So even though at the time it seemed like it was "The SAIL Content Model", it no longer is. To safeguard against the confusing changing of names, anything that is now considered "The SAIL X", should instead be given another name. And then they can be referred to as the current or recommended implementation of the "SAIL X". In the case of a Portal this seems particularly true because there are already multiple portals that work with SAIL. If what I'm writing above works for people, then we should spend some of the SAIL meetings trying to agree on what it means to be a SAIL Portal. Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
