-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -------- Original Message --------
Subject: [Spam]Re: [woas-dev] New storage format; was Re: Code updates
From: Paul Levey <p23y@...>
To: Wiki on a Stick (WOAS) Development <stickwiki-devel@...>
Date: Thu Feb 24 2011 03:46:01 GMT+0100 (CET)
>> Oh, and I was gonna say.
>>
>> Please don't change the simplicity of the way text is
>> stored in WoaS.
>> Watch "Surf's Up!" instead.
>
> (This is not meant as an answer to this email; it was simply triggered by it.)
>
> This is actually why I am still 80/20 in favour of dropping my involvement in WoaS after I finish my bug fixes (soon!) and starting a new project instead. (Being understood as to the "whys" of this thought continues to be way too important to me, I'm sorry to say, hence this note.)
>
Doesn't look like you considered the facts I have exposed in my previous email, in particular my "fade-out" crossing with your possible "fade-in".
> It seems to me that every aspect of WoaS (even the bugs!) has fervent supporters who will resist or detest even small changes to that aspect of the app. Perhaps they are using WoaS precisely because they love that particular aspect of it; a fix to them is a feature removed. I don't discount the validity of this, but the lack of a strong, cohesive, consistent, and foundational API in WoaS makes helping WoaS move forward very difficult, and such devotion to the status quo makes it difficult to imagine one coming into being without its being imposed by the project owner in the face of strong opposition.
>
I am sorry Paul but one cannot consider feedback on forums or mailing lists to make important choices, the majority of users does not communicate with the project and - although building up a community is important - the project manager shall not penalize those who cannot or do not want to partecipate in a feedback process.
Also I have not shown any opposition in my previous email, but the opposite. So I really can't figure out where this reply comes from as it looks like you did not even receive that message, is it possible?
> Philosophically, I think this is why open source is so very good at copying/implementing existing specifications with amazingly efficient bazaar-style development models, but rarely succeeds (or is incredibly slow) at innovation unless that innovation is simply presented to the project as complete "use-it-if-you-like-it---I-don't-care-either-way" implemented code, or has a design that is controlled by project owners and therefore presented to users in much the same way (WoaS has essentially been created this way, and I do understand why!).
>
> I am interested in advances that bring order of magnitude improvements in efficiency and usability; my desire to change the storage format (and parser/renderer) is motivated by such a result. It could, potentially, be implemented as an alternative, but I'd rather be working on these ideas with others who see the point of them and want to help me design and implement them -- a new project suggests itself again.
>
> I don't have time to "fight" for my vision of what's best and have discovered that it takes a great deal of time and energy to do so, even regarding seemingly simple issues, mostly just because of who I am as a person: someone who needs to explain and be understood. If I start a new project then "my" (even nascent) vision of how things should be done essentially becomes the specification that those attracted to that vision are attempting to design and implement, and the open source development model then applies and works very well. I cannot do all that I want to do by writing the code, or even the full specification, myself; I am already spread too thin!
>
I have never had nothing against forking the project, I have instead suggested to initially host the forks on the same project as "incubator"; an eventually successful fork could replace the main release and the developer would automatically become its project manager. I really see no "fight for power" in open source.
> On a general note, though, it seems to me that we shouldn't care about changes to internal format so long as the objects that implement that format enable us to load, identify, filter, transform, save, and otherwise use and manipulate that data as we desire (our single-file, internal content is, after all, essentially javascript code, not simple text). This is an essential feature of object-oriented design: information hiding. If I only use data through its API then the internal operations and data structures can change in all kinds of wonderful ways and I, as a consumer of that data or those services (as a user, author, designer, programmer, whatever), am completely unaffected. (A great example of this is the virtual file system API of Linux that enables continuing development and advancement of file storage technology while allowing users complete freedom as to which underlying features and formats they choose.)
>
Yes, that is the path I was trying to draw.
Kind regards,
- --
Daniele
> Kind regards, Paul.
>
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> stickwiki-devel mailing list
> stickwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/stickwiki-devel
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNZqo+AAoJEON28As9epPAts0H/iMX9L3OQTbLaT6UYH1gfBpj
pcmLLOLq1puBPowgjJZIHHviV83bBpAJ2gem+yiRygdf2hor7bzLjfAbSvEbv+ON
N25H1r/rj/79J0PXiyiwQXjLvvA+ikhGinVE1NzMX6J3Xvx9LLzxFC1yNa6wcdg1
qpi7xh6on/1Avk9voYySM3tHBklDv3ejbYK4DwXzejzvKHkrE50eojcvLMmETMo2
SvOgBaLayph6iNV11yWo/54hvVscsXla4H3aW4QxdmmV3K5P2yyB83SvCGpLvQoY
JYIdp7RykHuh6oAXkCAQnCVPNmih3iTAG6hAPCYoLrNzN9spJFsgvlowPfl0IaY=
=PPxv
-----END PGP SIGNATURE-----
|