On Jun 14, 2007, at 11:48 AM, Michael Pittaro wrote:

Daniel Krech wrote:
Hi all,

As of the last release we included an rdflib_tools top level
package to start gathering some unreleased tools people had around.
This was meant to be a temporary place holder until a separate project
could be created. Any reason not to split these off as a separate
project as planned? Main reason motivating the split now is an issue
that was hit with the debian packaging.

I think it would be good to keep the tools in the main distribution, as
examples of rdflib usage.  It also has the benefit of making sure the
tools are in sync with the current rdflib. The biggest limitation in
that case is release logistics, if the tools maintainers are a different
group, or the tools themselves get large enough to warrant a separate
project, then splitting make sense.

Sounds like a few more reasons to keep the tools a part of rdflib for now. And to date the developers are not a different group and the tools are not yet large enough to warrant a split. So, looks like we should plan on fixing the debian issue in the context of rdflib package.

mike
 I remember someone telling me they wanted to create such a project,
but don't remember who. Anyone wanting to start and lead such a
project? Else I'm willing to create a project at code.google.com that
we can move the rdflib_tools bits to.

Daniel Krech, http://eikeon.com/



--
[EMAIL PROTECTED]            http://www.snaplogic.org

Daniel Krech, http://eikeon.com/



_______________________________________________
Dev mailing list
Dev@rdflib.net
http://rdflib.net/mailman/listinfo/dev

Reply via email to