Yes, it could be a fair amount of work.
For the specific case of mentioning a release, I probably would not want
to increase the workload on a release manager to come up with more words
to describe future plans, use cases and similar details. With such a
channel, I would probably just be making sure that the release
announcement automatically appears there. This limits the usefulness
unless people are willing to put more time in generally.
Cheers,
Gary
On 23/01/13 13:17, Joachim Dreimann wrote:
I think blog postings could be a good way to get the word out on Bloodhound.
Running our own blog however is non-trivial in the ongoing commitment
required. We would also still need to build an audience, the lack of which
is the very reason I started this thread.
So instead I'd prefer if we contribute individual posts, or a series or
posts, to already established blogs - as guest authors for example? We
could approach any Trac, Python, ASF or Open Source Software blog for
example to see if they're interested. What about plugins we 'consume' or
the search library we're integrating? (Solr?)
- Joe
On 23 January 2013 12:13, Andrej Golcov <[email protected]> wrote:
What about establishing a BH blog with where we can share release
announcements with more details, describe use cases, future plans etc?
IMHO, blog presents information in more readable format than mail archive.
http://blogs.apache.org/ looks like an appropriate place for such blog.
Regards, Andrej
