In my view the only was a user supported community can sustain and
move forward over the long haul is by "taking a little, and giving a
lot more back" to that community and those that surround as well.
Can we take some of the ideas from here and other past attempts and re-
work them to make them better and easier to use?
This way people can find the answers they need to solve their problems
today .
Quick example recently I've shifted over to using FreeBSD for our
servers.
Without a doubt FreeBSD is one the core servers that has paved the way
for so many other servers to grow from given it's Unix core roots.
Today the internet is chocked full of information about FreeBSD.
Only problem is much if not all of the data out there is out date with
FreeBSD 9 let along 9.1
Which in many ways is making a shift from the older versions ......
every so subtly.
At this point all of this out dated information tends to point people
in the wrong direction and waste your time.
As with all things we need to move on and over to new idea and ways of
doing the same old thing.
Hmmmmm sounds just like Python to me, as we all stand in front of
moving on and over to Python 3.x
I think all of these ideas presented here so far are good.
But can we find a way to allow individuals to share snippets of code
and wisdom in such a way that can effectively harnesses the power of
collective "crowd sourcing" model over the long haul?
And also allows individuals to keep a personal view back on this effort?
I think allowing an individual to keep a personal index of bookmarks
makes it more powerful.
And will give people a reason to want to share and be apart of the
community.
You know the "one of for all and all for one thing" ....... comes to
mind making it a win-win case.
So far all the solutions out there fall short of this.
But there are many ideas from which we could look at to spring board
forward on to the next level if we think about it a bit more.
Stack exchange is an excellent idea that is far more effective than an
email support list could be.
Yet the problem is there still is no way to really organize this
wisdom collectively and keep it up to date.
Just the other day I was thinking what if all Python bloggers used the
same core blogging engine.
What if we take the idea of a "Wordpress platform" and focused it on
to the "Python topic"?
What I am driving at is can we define a "data model" that over time
can be refreshed style wise, but everyone writes to.
This way over time a "knowledge base standard" is being created that
can live on vs being lost like a 8 Track tape or a Word 1.0 Document.
Yes, Mike I would be interested in looking at ways of taking some of
your ideas or those of others on the list to see where we could end up.
As the collective power of a group focused on sharing surely will out
weight what an individual can do alone.
-Kevin
Kevin LaTona
STUDIO SOLA
Web | Mobile Development
Seattle WA USA
http://kevinlatona.com/
http://studiosola.com/
http://linkedin.com/in/kevinlatona
On Sep 5, 2012, at 8:09 AM, Andrew Beyer wrote:
On Wed, Sep 5, 2012 at 10:26 AM, Mike Orr <[email protected]>
wrote:
So, I propose a web-based oracle which would do the equivalent. It
would have multiple gangs: "Linux Answer Gang", "Python Answer Gang",
and potentially others. The public would submit questions, answerers
would answer them, and an editor would collect the monthly ones into
an "issue", and make an index of topics (a knowledge base).
Potentially the editor role could be automated, with "articles" on
the
side for human pontificating. The indexing role could also be
automated using tags. If anyone is interested in this, we can form a
group to explore it.
Interesting idea. I wonder if you wouldn't be better off building this
on top of one or more of the stackexchange sites...editing and
curating Q&A from there, rather than trying to build a new community
around this from scratch?
