So, tapestry has a twitter feed; I don't recall which address was used to set 
it up; possibly a novel/dummy address? It's set up with a "committers" list, 
which seems to work pretty well.

Robert

On Nov 3, 2011, at 11/38:31 AM , Christian Grobmeier wrote:

> On Thu, Nov 3, 2011 at 1:59 PM, Andrus Adamchik <[email protected]> 
> wrote:
>> On Nov 3, 2011, at 3:35 PM, Christian Grobmeier wrote:
>>> 
>>> A more concrete proposal:
>>> - utilize Twitter for interesting changes, builds anything which is to
>>> small to blog but shows activity on Cayenne
>> 
>> I am trying to use my personal Twitter exclusively for Cayenne: 
>> http://twitter.com/#!/andrus_a  Need to promote it more as well (add it to 
>> my email sig or something?). But maybe creating a project-controlled twitter 
>> is better on the long run.
> 
> 
> A discussion recently was on board@
> 
> Bertrand Delacretaz recommended on twitter:
> "AFAIK we don't have a foundation-wide policy, what seems important to
> me is that any PMC member can get the credentials, in case the current
> owner of those goes away.
> 
> It also makes sense IMO to coordinate "important" tweets (whatever
> that means) among the PMC members.
> 
> I don't know if it's practical to have the private@ list as the owner,
> IIUC it would then get notifications of retweets and such which might
> be noisy. If you require whoever owns the account to use their
> @apache.org address as the owner's address, worst case we could ask
> infra to extract mails sent from twitter to that address for password
> recovery, if that person's not available anymore and the PMC needs to
> get the credentials.
> 
> Just me personal advice, no official policy here."
> 
> 
> Shane followed up, recommended to respect the trademarks.
> That being said, a password shared between Cayeene-PMC members and the
> twitter account "apachecayenne" would make much sense!
> 
>>> I am willing to help in this area and write blog posts. Either on my
>>> blog (which has up to 5000 unique visitors a month) or on the asf blog
>>> or both.  But I need a bit guidances from the active developers, to
>>> spot interesting changes in time and to understand them quickly. A
>>> review of the posts before publishing would also not be so bad :-)
>> 
>> 
>>> - utilize Apache Blog for news
>>> 
>>> In addition I would like to start some kind of "Cayenne series" on my
>>> blog. Lets say 1 medium sized article all two weeks. For this I need
>>> some input about current changes or things of interest. Or even proof
>>> reading :-) I can also agree to co-writers and would accept complete
>>> articles from others.
>> 
>> Awesome! I think we have some interesting things to show right away. E.g. 
>> this thing about String IDs discussed in the parallel thread. In combination 
>> with map nature of DataObjects it allows to do some cool stuff. We can talk 
>> about using String IDs to refer to objects; building persistent "aspects" 
>> and attaching lifecycle to them with annotations; what can be done with such 
>> aspects; etc. All of this is still rather new and patterns and best 
>> practices are still being discovered (e.g. you can't do regular joins across 
>> aspect relationships, so how do you build your searches, etc.).
>> 
>> I am in love with this whole aspect stuff, as I am doing lots of commercial 
>> CMS programming based on Cayenne and relational DBs. But CMS systems require 
>> features more often associated with JCR (Jackrabbit) technology, rather than 
>> ORM. The above if done right allows to have the best of both ORM and JCR 
>> worlds.
>> 
>> Another area is DI configuration. We have a bunch of extension points now, 
>> so how do we take advantage of them to tune an application.
> 
> Oh wow, many ideas - tons of posts! And intersting stuff!!
> I am not sure where to start but I am willing to learn. We should make
> up a list of interesting topics and then look at it one by one. If I
> write them myself, I need a bit help to dig them out.
> 
> Cheers
> Christian
> 
> 
>> 
>> Andrus
>> 
>> 
>> 
>> 
> 
> 
> 
> -- 
> http://www.grobmeier.de

Reply via email to