incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@gmail.com>
Subject Re: Announcing releases: where our users are
Date Thu, 24 Jan 2013 00:39:34 GMT
I would recommend asking press@ what channels are available for pidlings.
They may be able to post to the main ASF twitter account.
On Jan 23, 2013 6:07 AM, "Gary Martin" <gary.martin@wandisco.com> wrote:

> Excellent. The suggested template for the announce message mentions the
> Trac project and so I hope that it is appropriate for all places we could
> want to announce it.
>
> As for the twitter account, it might be nice if this was also something
> that could effectively be done by a release manager. I'm not so much
> thinking of sharing the account details (although it could be useful to
> share those between more PPMC members just in case). I would probably
> prefer to just be able to send an email or even get the message
> automatically triggered by the announcement appearing on announce@
>
> The wikipedia idea sounds good too - certainly worth investigation. I
> would hope that copying the Trac entries and then updating as we officially
> gain specific features should not be too controversial. The guidelines for
> wikipedia discourage writing about anything you are directly involved in -
> even so, it would probably be better not to hide association of the project
> with such an addition.
>
> Cheers,
>     Gary
>
>
> On 23/01/13 08:37, Joe Dreimann wrote:
>
>> Ok, I will add trac-users@ to the list of places where we should
>> announce releases.
>>
>> I was hoping to add some more places though. Ryan set up an Ohloh profile
>> in the past [1], which may help people stumble across Bloodhound. I will
>> try and add it to the Wikepdia page comparing ticketing systems [2] (it
>> seems different enough to Trac in the features table).
>>
>> Are there mailing lists of python users that may be relevant?
>> Specific forums or blogs? Olemis has been doing some promotion that way
>> in the past [3], which is great in my opinion.
>>
>> - Joe
>>
>>
>> [1] http://www.ohloh.net/p/apache-**bloodhound<http://www.ohloh.net/p/apache-bloodhound>
>> [2] http://en.m.wikipedia.org/**wiki/Comparison_of_issue-**
>> tracking_systems<http://en.m.wikipedia.org/wiki/Comparison_of_issue-tracking_systems>
>> [3] http://simelo-es.blogspot.co.**uk/2012/08/tuxinfo-50-apache-**
>> bloodhound-un-fork-de_12.html<http://simelo-es.blogspot.co.uk/2012/08/tuxinfo-50-apache-bloodhound-un-fork-de_12.html>
>> ________________________
>> @jdreimann - Twitter
>> Sent from my phone
>>
>> On 23 Jan 2013, at 07:07, Greg Stein <gstein@gmail.com> wrote:
>>
>>  On Jan 23, 2013 1:20 AM, "Ryan Ollos" <ryan.ollos@wandisco.com> wrote:
>>>
>>>> On Tue, Jan 22, 2013 at 4:26 PM, Olemis Lang <olemis@gmail.com> wrote:
>>>>
>>>>  [...]
>>>>>
>>>>> FWIW , I do . I wonder whether I've also seen rjollos around ... or
>>>>> maybe it's just a figment of my imagination ? It's just that I confuse
>>>>> trac-users@... with trac-dev@...
>>>>>
>>>> You are not imagining. I follow both lists and I haven't seem any
>>>> negative
>>>> reactions to mentions of Bloodhound. I would be very surprised to see
>>>> negative reactions since we push fixes back to Trac, etc...
>>>>
>>> I think that as long as the project gives due credit back to Trac, then
>>> we
>>> can use trac-users. We are not a corporation, but another OSS project.
>>> People generally get bothered about corps, not other open source
>>> projects.
>>>
>>> *IF* a problem arises, then we can discuss with the trac-users community,
>>> on how to amend the process.
>>>
>>> At this point, given that plugins/etc announce there, and that a prior
>>> announced didn't generate an uproar, it looks like a great forum.
>>>
>>> Cheers,
>>> -g
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message