Hi Paul,

when I wrote

"It would be interesting for the community to know what is going on
behind the scenes with BT and Unamesa, to be privy to conversations
and debates and to be able contribute."

... the word 'interesting' was not meant to allude to anything
sinister. Rather 'interesting' from a business structure point of
view. I've had discussion about ideas with a few innovation academics:
the think i am on another planet when i tell them  the Tiddly IP is
owned by a charity. They don't believe me when I tell them about the
TW project.

I can't contribute code, but have a research interest in creativity
and organisational structure. I thought that I would be able to help
in some way. I do appreciate that there is a difference in asking
questions and delving into the workings of companies; the business of
a business is their own business. I am not wanting to butt in, but i
think that there is some genuinely interesting new ground and a model
for community organisaton and cooperation that could be applied
elsewhere.

Is it common for Open Source projects? Is it common in R&D in companies like BT?

Alex
----

When

2009/2/21 Paul Downey (psd) <paul.s.dow...@gmail.com>:
>
> On Feb 21, 10:43 am, Alex Hough <r.a.ho...@googlemail.com> wrote:
>
>> With the unusual structure of the TiddlyWiki project, some interesting
>> governance issues arise.
>> Would it be in appropriate for these issues to be  discussed on the group?
>>
>> It would be interesting for the community to know what is going on
>> behind the scenes with BT and Unamesa, to be privy to conversations
>> and debates and to be able contribute.
>
> Crumbs that sounds quite sinister! Speaking for myself, and not for
> BT, from where I sit the only thing going on behind closed the scenes
> are stuff you'd expect to go on behind closed doors, e.g. sponsorship.
> Beyond that I'm unaware of any hidden hand. There are no meetings in
> Area 51. There is no Grassy Knoll :) If that doesn't reassure you,
> then I suggest you start a thread with some specific concerns and we
> can get someone from Osmosoft and UnaMesa to answer them.
>
> Note: if it's the technical direction of TiddlyWiki which worries you,
> then that's a very different issue. TiddlyWiki is a fairly typical
> Open Source project in that the direction is steered by developers
> contributing trac tickets, patches, code, and Jeremy as our BDFL
> taking editorial control. We now have other core committers including
> Martin Budden and FND, but it's Jeremy who ultimately decides which
> contributions are released and which remain as plugins, extensions and
> forks. That path continues to be very transparent, and observable from
> trac: http://trac.tiddlywiki.org/
>
> As in most any decision process there are discussions behind those
> decisions taking place on trac, this and the developer mailing lists,
> on irc, directly over email, IM and face to face discussion, sometimes
> over frothy drinks. It's not always to the satisfaction of everybody,
> but in life, nothing ever is! If you want to influence the discussion,
> it's simple: choose a venue which suits you and continue to
> contribute!
>
> Paul (psd)
> --
> http://blog.whatfettle.com
> >
>



-- 
t: 0161 442 2202
m: 0781 372 50 17
skype: alexhough
delicious: alexhough

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to 
tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to