Re: State of Development
Matthias L. Jugel <leo <at> mud.de>
2006-06-14 18:51:36 GMT
Hello,
actually, we still develop on SnipSnap and try to find the best way
to handle the project in future. Our difficulty is that most projects
we have to work for at the moment do not involve SnipSnap. The idea
Dirk has would help alot either keeps us working full-time at the
project. We have different directions possible, ranging from plain
team communication to knowledge management.
What we offer right now is that interested parties can help
development by taking over certain modules of SnipSnap. We are in the
process of extracting modules, like the storage backend (for
different dbs etc.), some of the macro packages and one of the big
issues is the web frontend which must move to a better framework.
Leo.
On 14.06.2006, at 19:55, Dirk Riehle wrote:
> So, Matthias and Stephan are obviously quite busy. (So busy, they
> didn't even advertise the Wiki Symposium here, which they are
> helping.)
>
> I'm curious to ask the community on this list. Should these two guys
> go out and find a corporate sponsor that employs them fulltime to
> work on SnipSnap (or something like it)?
>
> What would that mean for a license change? Away from GPL (for
> SnipSnap) towards what? What would you like to see to make SnipSnap a
> successful OSS project the way you like it.
>
> Thanks,
> Dirk
>
>
>
> At 14.06.2006, Jan Grant wrote:
>> On Wed, 14 Jun 2006, Jan Galinski wrote:
>>
>>> Hi everyone ,
>>>
>>> I just installed snipsnap and want to use it as a personal "keep and
>>> manage" tool for notes, ideas, tutorials etc.
>>> I have some ideas for further dev (like latex export, some macros,
>>> syntax extensions) but after looking at snipsnap.org and
>>> radeox.org I
>>> am beginning to doubt that this project is still alive.
>>>
>>> So my question: Is there continuous development of snipsnap and
>>> radeox? Can one expect that an active community will share themes,
>>> macros , discuss directions and so on?
>>> I dont want to store all my information in a dead system and migrate
>>> in a few month.
>>
>> I think the problem is that snipsnap has never really geared up to
>> working with external collaborators: whatever source-code
>> reorganisations are required to make this possible just don't
>> appear to
>> have happened.
>>
>> The above statement may not be true: however it reflects my
>> perception
>> as a developer who would be interested in getting involved with the
>> project. I think that perception needs addressing as the top
>> priority if
>> snipsnap is to gain any momentum.
>>
>>
>> --
>> jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/
>> Tel +44 (0)117 3317661 http://ioctl.org/jan/
>> Donate a signature: http://ioctl.org/jan/sig-submit
>> _______________________________________________
>> SnipSnap-Users Mailing List
>> snipsnap-users <at> snipsnap.org | http://snipsnap.org/
>> http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
>
> _______________________________________________
> SnipSnap-Users Mailing List
> snipsnap-users <at> snipsnap.org | http://snipsnap.org/
> http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
--
--
Mud.DE -- Gemeinschaft Virtueller Welten Deutschland
Matthias L. Jugel http://www.mud.de Info: info <at> mud.de
_______________________________________________
SnipSnap-Users Mailing List
snipsnap-users <at> snipsnap.org | http://snipsnap.org/
http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users