I can see lots of places that we can use the kind of structure that we
have set up in the Fedora Create wiki to foster more collaboration
between the groups, even across the whole repository community more
generally. Many of the areas that we have defined initially cover
software that isn't really specific to Fedora, but that the community
is concentrating around. An obvious example would be workflow stuff,
but there are lots more.
The diagram that you refer to actually needs some work even from the
Fedora viewpoint. It was created early in our discussions, before we
were thinking of the core repository team as a special case of a group
within the larger Fedora Create community, and doesn't reflect that
orientation. Perhaps there is a way forward here in thinking of the
"DuraSpace Create" developers community more generally, with areas for
Fedora- or DSpace-specific stuff.
To be honest, I am really focused on getting a useful way of
organizing the Fedora developers community to build on the momentum
that has developed so far. The fact that Fedora is a foundation for
many applications, but not a complete solution for any one of them,
has resulted in a more amorphous community than has evolved around
DSpace. I don't want to do anything to complicate that process, but I
think that with some thought we can organize this so that we serve the
full community better.
I have copied Val on this message, so let me talk to her and we will
think about a way to get a start on some discussion around this idea.
I think that it is definitely something to move on soon.
Director of Community Strategy and Alliances
Director of the Fedora Project
tstaples@... (202) 684-6952
skype: thorny.staples http://www.duraspace.org
On Nov 24, 2009, at 10:50 AM, Mark Diggory wrote:
> I think this is a great endeavor, I hope we can start to find
> synergies between this new space and the DSpace community. I
> certainly hope we can combine our efforts on the wiki and
> communication fronts so that it can foster greater collaboration
> between the groups. I know we on the DSpace side are always looking
> for better tools for managing the community. I for one think that
> settling on one wiki, Confluence, can be an opportunity to bring the
> communities much closer together. Chris setup a space for us
> sometime back and I did some initial experiments with porting
> mediawiki to confluence that seemed promising (but need more
> resources to get completed)...
> I will add that it would be great to see us start to place the
> DSpace community into some of this work you doing. For instance,
> The following diagram would be well served to include a top level
> trunk/branch with the DSpace community within it.
> Perhaps a forum that bridges the two groups can help us start to
> work together more. One of the key aspects of DSpace is the constant
> Asynchronous nature of its collaboration. Will a large community
> around the world, everyone making a fixed meeting time is not always
> possible. To foster collaboration, its important to find avenues
> that discussion avenues are not restricted temporally/geographically.
> Recently in our own IRC meetings, we decided that the idea of
> subject meetings once a month would be very valuable. I think
> having some of these meetings be aligned with the fedora teams
> subject meetings such that both groups would be present in the
> topics (DSpace 2.0 / Fedora GSoC project, JCR Connectors, DSpace
> 1.x / Fedora, Solr, etc) would be a great initial starting point.
> On Mon, Nov 23, 2009 at 6:07 AM, thornton staples <tstaples@...
> > wrote:
> In the continuing effort to move the Fedora project from being the
> funded development project were it started, to a completely
> community-based effort, I invite you to visit the new "Software"
> page on the Fedora Commons web site (http://www.fedora-commons.org/software
> Chris Wilper, Matt Zumwalt and I developed this new way of looking
> at the Fedora Create community as a whole effort, including both the
> Fedora Repository Service, and all of the software that everyone is
> developing on top of it, in one complete view. Please think of it as
> a starting point, a suggestion for how to proceed. From the software
> page down, everything is in the Fedora wiki. We want to take a
> pragmatic view of all of this, the structure we have organized can
> change as appropriate. We will follow the "wiki gardening" approach,
> that encourages everyone to add the information that they think is
> important, not worrying too much about the formalities. Wiki
> gardeners will come back and re-organize the wiki, weeding and
> transplanting as necessary and desirable.
> The view of the Fedora Create community is presented by sorting the
> software development into categories to try to make it more
> manageable. These categories can be tweaked and changed, or added to
> as necessary. In general, each category includes a registry where
> everyone can list software that they have developed that they would
> like to share, as well as areas where we can discuss hot topics,
> share information about standards, list good ideas for new software,
> etc. I strongly encourage everyone to tell us about the software
> that you have developed, are developing or would like to see
> developed, in each category. Please use the registry to list
> software projects that are underway, as well as those that are
> created; it is very useful to all of us to know what people are
> working on, as well as what is available now.
> The core Fedora Repository Service must be treated as a special case
> in this view of the software and the developers community. It is the
> foundation for everything that we are doing. We have a committers
> group that will be the keepers of the core. I am very pleased to be
> able to say that Chris has rapidly developed this group to be more
> community-oriented already. We have 11 committers now, 8 of them are
> not DuraSpace employees. The next release of Fedora, 3.3, is being
> managed by Kai Strnad (thanks to FIZ Karlsrhue for giving his time!)
> and is planned to come out by the end of the year.
> It would be really good to begin to consolidate our wiki around this
> evolving model. We have begun to move stuff from the developers
> forum area already. The area for ideas and discussion around the
> repository service is still being developed, but the rest of the
> Fedora Create area is ready to go. I have moved and updated much of
> the content model stuff already, and Dan Davis is working on getting
> all of the info related to workflow issues moved. If any of you has
> information that you have been building on the wiki, especially
> recently, I encourage you to find a place on the new pages for it.
> If you don't see a good place for it right now, let me know.
> Lastly, if any of you out there are particularly good at, and/or
> interested in, helping keep up the wiki more generally, both in
> weeding and transplanting, as well as in guiding the on-going
> process to develop better organization, please talk to me. I think
> that we could all benefit from an organized wiki-gardeners group!
> Thornton Staples
> Director of Community Strategy and Alliances
> Director of the Fedora Project
> DuraSpace, Inc.
> tstaples@... (202) 684-6952
> skype: thorny.staples http://www.duraspace.org
> Mark R. Diggory
> Head of U.S. Operations - @mire
> http://www.atmire.com - Institutional Repository Solutions
> http://www.togather.eu - Before getting together, get Tog@...