When you want final forms, you produce something static. There are many reasons why this is done. One reason is to create a final version and create a collection of articles and calling it a book. Such books can be priced and it is quite legitimate to sell them on ebay. This has been done and when another such publication is found there are usually some people who complain about it.
For Wikisource and Wikibooks however there are finished products. In Wikisource a project can be considered finished once the proof reading of a digital text has been completed of what started as a scanned text. Only when it is finished, it is ready for easy public consumption.
What Wikisource does is provide the tools for this process. Essentially Wikisource serves a community that is engaged in a workflow. What it does not do so well is publish the finished products and find an audience for them.
The work at Wikisource is important. Its finished products are relevant and they are worthwhile. They fit in our aim to share in the sum of all knowledge. We can give things away, we can ask for a contribution but we owe it to our public that we make a best effort in making all this knowledge we are the custodian of easily accessible.
We may need a new project .. "Wikipublish" where we publish final versions of our "Wikisources". Where we publish collections of Wikipedia articles. Where we publish our "Wikibooks". We do not need much marketing, we need to make our finished goods available to a public and provide it in a format that it finds easy to digest.
Thanks,
GerardM
15 comments:
As I just wrote in this blog article, its less about "final" but about delivering content in reusable forms. It should be easy to link to and get Wikipedia articles, Wikiquote quotations, Wikibook books, Wikisource publications etc. at every stage of development. Making content "final" should be no more than setting a flag, such as known from flagged revisions. So in my opinion there is no need for "Wikipublish" but for better content delivery in existing projects.
At that time several Wikipedias were created that were not recognised as a language. In the mean time several of these have been recognised as a language and as a consequence have their own code.
There is something about a part of us continuing into the future long after we are gone that appeals to us.
Only when it is finished, it is ready for easy public consumption.
One reason is to create a final version and create a collection of articles and calling it a book.
This has been done and when another such publication is found there are usually some people who complain about it.
Essentially Wikisource serves a community that is engaged in a workflow. What it does not do so well is publish the finished products and find an audience for them.
In the mean time several of these have been recognised as a language and as a consequence have their own code. 8
This has been done and when another such publication is found there are usually some people who complain about it.
There is something about a part of us continuing into the future long after we are gone that appeals to us.
Essentially Wikisource serves a community that is engaged in a workflow. What it does not do so well is publish the finished products and find an audience for them.
This has been done and when another such publication is found there are usually some people who complain about it.
What it does not do so well is publish the finished products and find an audience for them.
Essentially Wikisource serves a community that is engaged in a workflow. What it does not do so well is publish the finished products and find an audience for them.
In the mean time several of these have been recognized as a language and as a consequence have their own code.
Post a Comment