What is legally permissible when adding a copyright notice to a derivative work?In 2008 I stopped contributing to an open source project when it was pwned by a commercial interest. At that time a number of my original works existed in their source code repository, and still exist there pretty much as I left them 2 years ago, when I moved further development to a different repository. All of these works were released under the GPL, and carry my personal copyright notice, or that of a wider group of contributors who had worked on the project up to that date. Since I left the project, the now-owners have redefined that contributors group, and have taken to retrospectively applying a different copyright to a number of these works. They have made some minor changes (mostly removing my personal branding, but also adding some scraps of new documentation) and added a dated copyright notice of their own that extends their claim back several years, despite the fact that (according to their own public records) no changes have been made until very recently. Now, all the code and documentation is in their source code repository, so I would have no problem proving that I am the original copyright holder. However by making some very small changes, they have technically created a derivative work, and I don't have any problem with them adding a copyright notice to cover these new changes. But what I find really objectionable is the dating of that new copyright notice back to a point well before the changes (5 years before, in at least one case). This is obviously immoral, but the question is, is it actually illegal? Update: it has come to light that in at least one case (not my code) the new copyright notice has been extended back to a date before the work was first published. I'm not sure whether to laugh or cry! Tags: collaboration, community, copyright
The WebDAV support for Foswiki took another leap forward this morning, when we finished development of a new FilesysVirtualPlugin which supports different views for topics. This makes Foswiki topic content much more accessible to a wider range of tools.Some time ago we (C-Dot Consultants and Kontextwork) jointly released the WebDAVContrib and FilesysVirtualPlugin, which together support access to Foswiki data via the WebDAV protocol. More recently we released the WebDAVLinkPlugin, which enhances the integration of WebDAV documents into Foswiki, by allowing links to WebDAV documents to be edited using native applications on the client, such as the Microsoft Office™ suite. That's great for working with attachments, but what about topics? Up to now, if you wanted to edit a topic, you had to edit the raw Topic Markup Language (TML) that the topic was stored in. Using Microsoft Word to edit TML is like using the space shuttle to commute 2km to work. Life would be much simpler if we could feed Word with a format it understands, like HTML. We've been able to WYSIWYG edit Foswiki topics in the browser for a long time now; so the technology to convert topic content to other formats and back again exists; all we needed was a way to present this through WebDAV. What we need to do is to give the WebDAV user a way to select what format they want the topic in. We've done this by allowing the same topic content to be mapped to more than one file entry in a WebDAV directory listing; each file entry is referred to as a "view" (because it's just a different way of looking at the same data). The FilesysVirtualPlugin is configured with a list of views that it supports; for example, txt, html, json. When it is asked for a list of files in a Foswiki web, it generates a file entry for each of the different views, so the topic MyTopic ends up with the entries:
MyTopic.txt
MyTopic.html
MyTopic.json
These file entries can be read and written just like normal files; the FilesysVirtualPlugin takes care of mapping the content back to TML. Because these file entries are all views of the same data, then if you edit MyTopic.txt, then MyTopic.html automatically changes too, and vice-versa. Besides txt, html, and raw, two meta-data views have been provided, json and perl. These views allow you access to topic meta-data. It's easy to add new views, and we foresee other useful view types, such as xml and yaml coming along later. WebDAVContrib, FilesysVirtualPlugin and the companion WebDAVLinkPlugin are available from Kontextwork. Tags: ajax, foswiki, webdav, wysiwyg
It is often claimed that only a few developers moved from TWiki to Foswiki, therefore the first article will look at who are/were active core developers of both projects.
Number of core developers
The analysis focus on core development of both projects, as this is a major indicator for the health of a software project. This is because you need a lot more knowledge and background for developing the core product than for writing an extension with a clearly defined API.
Claim
"We have healthy downloads, an active user community, and a very active support community. However, we are a smaller developer community than we used to be." Source: Blog post by Peter Thoeny (Twiki.net) – 11 Nov 2009
Fact
Developers of TWiki and Foswiki
Core contributers
PeterThoeny
SopanShewale
CrawfordCurrie
CrawfordCurrie
KoenMartens
KoenMartens
MichaelDaum
MichaelDaum
RafaelAlvarez
RafaelAlvarez
AndreUlrich
AndreUlrich
TravisBarker
TravisBarker
ArthurClemens
ArthurClemens
GilmarSantosJr
GilmarSantosJr
LynnwoodBrown
LynnwoodBrown
OliverKrueger
OliverKrueger
ColasNahaboo
ColasNahaboo
KennethLavrsen
KennethLavrsen
MarkusUeberall
MarkusUeberall
SvenDowideit
SvenDowideit
AntonioTerceiro
AntonioTerceiro
WillNorris
WillNorris
MartinCleaver
MartinCleaver
New to core development
SebastianKlus
SebastianKlus
OlivierRaginel
OlivierRaginel
EugenMayer
EugenMayer
LarsEik
LarsEik
IsaacLin
IsaacLin
GeorgeClark
GeorgeClark
AndrewJones
AndrewJones
New developers
SeanMcCarthy
RobManson
BenBeijer
RaulFRodriguez
MarkSchumann
MichaelTempest
AndrewPantyukhin
DrakeDiedrich
PaulHarvey
2 Core Contributers
32 Core Contributers
Statement
Developer community:
Look at the list of developers contributed to the core of both projects since the commercial takeover of Twiki.net. The TWiki.org development community has dropped to almost nothing – only Peter and his employee Sopan is left. Whereby all other TWiki.org core developers moved to Foswiki.org. Together with new developers, Foswiki has almost doubled its core contributors!
Number of core contributors
before commercial takeover of TWiki.org (2008-10-27)
one year later (2009-10-27)
TWiki.org
18
2
Foswiki.org
n/a
32
Healthy Downloads:
Yes, lots of users still download the old TWiki code as they don´t know about Foswiki and its progress. Our marketing was very bad as we are better in concentrating on improvements than in talk about it. Sadly even most of our old TWiki user community don´t know about Foswiki and may wonder why there is no progress on TWiki.org.
Sources
As the analysis is based on open source, you can easily check the correctness of the data by yourself. For the first analyzation I used the following sources:
The WebDAV support for Foswiki took another leap forward this morning, when we finished development of a new FilesysVirtualPlugin which supports different views for topics. This makes Foswiki topic content much more accessible to a wider range of tools. Tags: ajax, foswiki, webdav, wysiwyg
It is often claimed that only a few developers moved from TWiki to Foswiki, therefore the first article will look at who are/were active core developers of both projects. Tags: community, foswiki, opensource, twiki
Thanks I think im gonna start a wiki for web hosting. Could any one point me at a link for a how to on getting started. Which interface to use ..etc. Thank you Paula J
Aron, thanks for your warm words about TWiki. We still appreciate it, as we are all still deeply linked to our roots. These are roots that we left behind now as we build up the TWiki successor called Foswiki right now. Thanks also for offering that we all are welcome to come over to DekiWiki. I really am a fan of DekiWiki and highly appreciate the gr8 work MindTouch does to produce such a high quality product. However, TWiki somewhat became our second nature, so most, if not all developers stay on course doing whatever we always did, just faster and not threatened by Peter's trademark. I only wished he would not see a need to turn around and use the trademark against the core of TWiki, its own community. That was not for the best of the project for sure. Peter obviously did not assess the situation clear enough coming to the conclusions and actions as outlined in the above posting. Most probably, this is not for the best of TWiki.net either, as it might have become "radioactive" for more venture investments. They might milk the open sources for some time but the product already starts to rotten with TWiki.net not able to execute. Not so Foswiki. The number of people that take part is just amazing as proven by pure number of submissions in the recent surveys to find the new brand name. TWiki was in the transition from one governance model with a sole dictator to another one with an elected board of directors and an association to promote the project and take care of legal matters. This process failed and Peter installed an even more restrictive dictatorship by ruling the project from within his new company called TWiki.net. Frankly, we have seen this coming and we tried to keep the project true Open Source. From TWiki's perspective we failed. From Foswiki's perspective we now work unleashed from the curse of a bad governance structure. Just have a look at http://foswiki.org. This new old community is working like crazy to get the new release out. And we will do it. It will be a much better wiki than TWiki ever was. All of the roadmap for TWiki-5 will be executed on Foswiki. The Foswiki Association, the formal body for this project, will come to live very soon. So basically, we just get what we want. It only needs a bit more work. All these efforts are more than worth it as the new site already shows. And we just started. This is only weeks ago and look at it… Note, that these are the same people that have formerly been known as the TWiki community. Just imagine how badly TWiki was managed looking at the unleashed energy and abilities that people can now unfold on the new project. And we are not done with it. It's renovation & innovation time.
What is legally permissible when adding a copyright notice to a derivative work?In 2008 I stopped contributing to an open source project when it was pwned by a commercial interest. At that time a number of my original works existed in their source code repository, and still exist there pretty much as I left them 2 years ago, when I moved further development to a different repository. All of these works were released under the GPL, and carry my personal copyright notice, or that of a wider group of contributors who had worked on the project up to that date. Since I left the project, the now-owners have redefined that contributors group, and have taken to retrospectively applying a different copyright to a number of these works. They have made some minor changes (mostly removing my personal branding, but also adding some scraps of new documentation) and added a dated copyright notice of their own that extends their claim back several years, despite the fact that (according to their own public records) no changes have been made until very recently. Now, all the code and documentation is in their source code repository, so I would have no problem proving that I am the original copyright holder. However by making some very small changes, they have technically created a derivative work, and I don't have any problem with them adding a copyright notice to cover these new changes. But what I find really objectionable is the dating of that new copyright notice back to a point well before the changes (5 years before, in at least one case). This is obviously immoral, but the question is, is it actually illegal? Update: it has come to light that in at least one case (not my code) the new copyright notice has been extended back to a date before the work was first published. I'm not sure whether to laugh or cry! Tags: collaboration, community, copyright
The WebDAV support for Foswiki took another leap forward this morning, when we finished development of a new FilesysVirtualPlugin which supports different views for topics. This makes Foswiki topic content much more accessible to a wider range of tools.Some time ago we (C-Dot Consultants and Kontextwork) jointly released the WebDAVContrib and FilesysVirtualPlugin, which together support access to Foswiki data via the WebDAV protocol. More recently we released the WebDAVLinkPlugin, which enhances the integration of WebDAV documents into Foswiki, by allowing links to WebDAV documents to be edited using native applications on the client, such as the Microsoft Office™ suite. That's great for working with attachments, but what about topics? Up to now, if you wanted to edit a topic, you had to edit the raw Topic Markup Language (TML) that the topic was stored in. Using Microsoft Word to edit TML is like using the space shuttle to commute 2km to work. Life would be much simpler if we could feed Word with a format it understands, like HTML. We've been able to WYSIWYG edit Foswiki topics in the browser for a long time now; so the technology to convert topic content to other formats and back again exists; all we needed was a way to present this through WebDAV. What we need to do is to give the WebDAV user a way to select what format they want the topic in. We've done this by allowing the same topic content to be mapped to more than one file entry in a WebDAV directory listing; each file entry is referred to as a "view" (because it's just a different way of looking at the same data). The FilesysVirtualPlugin is configured with a list of views that it supports; for example, txt, html, json. When it is asked for a list of files in a Foswiki web, it generates a file entry for each of the different views, so the topic MyTopic ends up with the entries:
MyTopic.txt
MyTopic.html
MyTopic.json
These file entries can be read and written just like normal files; the FilesysVirtualPlugin takes care of mapping the content back to TML. Because these file entries are all views of the same data, then if you edit MyTopic.txt, then MyTopic.html automatically changes too, and vice-versa. Besides txt, html, and raw, two meta-data views have been provided, json and perl. These views allow you access to topic meta-data. It's easy to add new views, and we foresee other useful view types, such as xml and yaml coming along later. WebDAVContrib, FilesysVirtualPlugin and the companion WebDAVLinkPlugin are available from Kontextwork. Tags: ajax, foswiki, webdav, wysiwyg
Thanks I think im gonna start a wiki for web hosting. Could any one point me at a link for a how to on getting started. Which interface to use ..etc. Thank you Paula J
About
You are in the page section consisting of all the
BlogPages that
exist outside the chronological sortion of BlogEntries but are special
TWikiTopics with respect to this application