I tried to figure if I could do anything to fix "www.cherokee-project.com/community.html". But as far as I can see, this is something I cannot fix because it requires knowledge about the web server and ssh access.
Then I thought about all the different places where you could discuss anything related to Cherokee.
That is:
- This mailing list (cherokee@lists.octality.com)
- The Google Group (https://groups.google.com/forum/?fromgroups#!forum/cherokee-http)
- Facebook (https://www.facebook.com/cherokee.project)
- Google+ (https://plus.google.com/u/0/communities/109478817835447552345)
- Google Code (http://code.google.com/p/cherokee)
- Twitter (https://twitter.com/webserver)
And there are several bug tracker I know of:
- Google Code Issues (http://code.google.com/p/cherokee/issues)
- Github Issues (https://github.com/cherokee/webserver/issues)
- Debian Bugtracker (http://bugs.debian.org/cherokee)
Then there is also:
- http://planet.cherokee-project.com/
And of course the broken Community page:
- Cherokee Community (http://www.cherokee-project.com/community.html)
-- REGARDING COMMUNITY ACCESS--
*** I believe we can create a better public appearance if we concentrate our energy on one place. ***
If we focus on few things, rather than occupying a place everywhere possible, not only do we get a higher level of attention, but we also have to invest less energy.
The positive thing is, that almost anybody has easy access to the community without registering. But also that not anybody will read any
contribution (might it be a feedback, bug report, anything) because
someone might not be part of the platform it's been contributed to
(Mailing list <-> Facebook <-> Google for example).
Being on Facebook, Google+ (As a page/group and community) and Twitter means that we must communicate everything in all channels at once. If you neglect one channel, its users will think the Project is neglected (which is not true, of course).
Then there is planet.cherokee-project.com. In my eyes this should be closed. Recent posts are non-english and there has been nothing new for almost one year. I also think that it's better to integrate a blog into the main page if it's about Cherokee.
Now the
mailing list is obviously the place to be if you need information or
have something to discuss. My personal opinion is, that mailing lists server their purpose well, but they are so 1980's ;) I believe many people don't want to use it because they don't know the technology. Now there was a community page on "www.project-cherokee.com" that is not working anymore. My guess is, that this has been a forum.
-- REGARDING BUG TRACKERS --
There are three bug trackers, I don't know if thats that now too much. The on Github should be the one, but as far as I can see it's a very basic one. The one on Google Code is good, but I find it wierd because Cherokee has nothing to do with Google. Doesn't that also cause a lot more effort? That's from a non-developers point of view, so it might be inaccurate. I can't really do a constructive critic, it's just an observation.
-- IDEAS --
Let's be more talkative towards the public. Anything you want to share should be shared in any channel, or shut down neglected channels (Twitter sucks anyway IMO ;)). Here I offer my help: I am no marketing person, but I can offer to distribute any words you send me throughout FB/G+/T in the form of a small article.
While it's easier for someone to migrate from a mailing list to a forum, than vice versa, I think it could help the Project become more popular if there would be ONE forum where all the discussion go. That forum has to be advertised everywhere (FB/G+/Groups/Mailinglist/T, etc). Here I offer my help, too. What I can do is setting up a forum on my webserver so the Community-Part of cherokee-project.com can be reinstated. As long as there is no heavy usage (100+ members constantly posting), I think my server can handle that extra load.
Shut down planet.cherokee-project.com for the sake of not appearing inactive.
-- IDEAS FROM A NON-PROGRAMMERS VIEW --
Reintroduce version numbers. Just for the sake of looking active on the website. After a new version is announced, pack the sources and upload them on the website.
-- OR ELSE --
If you have any other ideas I can contribute, let me know. I don't have much time, but I like to help a bit.
- Stadtpirat11
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee
Then I thought about all the different places where you could discuss anything related to Cherokee.
That is:
- This mailing list (cherokee@lists.octality.com)
- The Google Group (https://groups.google.com/forum/?fromgroups#!forum/cherokee-http)
- Facebook (https://www.facebook.com/cherokee.project)
- Google+ (https://plus.google.com/u/0/communities/109478817835447552345)
- Google Code (http://code.google.com/p/cherokee)
- Twitter (https://twitter.com/webserver)
And there are several bug tracker I know of:
- Google Code Issues (http://code.google.com/p/cherokee/issues)
- Github Issues (https://github.com/cherokee/webserver/issues)
- Debian Bugtracker (http://bugs.debian.org/cherokee)
Then there is also:
- http://planet.cherokee-project.com/
And of course the broken Community page:
- Cherokee Community (http://www.cherokee-project.com/community.html)
-- REGARDING COMMUNITY ACCESS--
*** I believe we can create a better public appearance if we concentrate our energy on one place. ***
If we focus on few things, rather than occupying a place everywhere possible, not only do we get a higher level of attention, but we also have to invest less energy.
The positive thing is, that almost anybody has easy access to the community without registering. But also that not anybody will read any
contribution (might it be a feedback, bug report, anything) because
someone might not be part of the platform it's been contributed to
(Mailing list <-> Facebook <-> Google for example).
Being on Facebook, Google+ (As a page/group and community) and Twitter means that we must communicate everything in all channels at once. If you neglect one channel, its users will think the Project is neglected (which is not true, of course).
Then there is planet.cherokee-project.com. In my eyes this should be closed. Recent posts are non-english and there has been nothing new for almost one year. I also think that it's better to integrate a blog into the main page if it's about Cherokee.
Now the
mailing list is obviously the place to be if you need information or
have something to discuss. My personal opinion is, that mailing lists server their purpose well, but they are so 1980's ;) I believe many people don't want to use it because they don't know the technology. Now there was a community page on "www.project-cherokee.com" that is not working anymore. My guess is, that this has been a forum.
-- REGARDING BUG TRACKERS --
There are three bug trackers, I don't know if thats that now too much. The on Github should be the one, but as far as I can see it's a very basic one. The one on Google Code is good, but I find it wierd because Cherokee has nothing to do with Google. Doesn't that also cause a lot more effort? That's from a non-developers point of view, so it might be inaccurate. I can't really do a constructive critic, it's just an observation.
-- IDEAS --
Let's be more talkative towards the public. Anything you want to share should be shared in any channel, or shut down neglected channels (Twitter sucks anyway IMO ;)). Here I offer my help: I am no marketing person, but I can offer to distribute any words you send me throughout FB/G+/T in the form of a small article.
While it's easier for someone to migrate from a mailing list to a forum, than vice versa, I think it could help the Project become more popular if there would be ONE forum where all the discussion go. That forum has to be advertised everywhere (FB/G+/Groups/Mailinglist/T, etc). Here I offer my help, too. What I can do is setting up a forum on my webserver so the Community-Part of cherokee-project.com can be reinstated. As long as there is no heavy usage (100+ members constantly posting), I think my server can handle that extra load.
Shut down planet.cherokee-project.com for the sake of not appearing inactive.
-- IDEAS FROM A NON-PROGRAMMERS VIEW --
Reintroduce version numbers. Just for the sake of looking active on the website. After a new version is announced, pack the sources and upload them on the website.
-- OR ELSE --
If you have any other ideas I can contribute, let me know. I don't have much time, but I like to help a bit.
- Stadtpirat11
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee