Dual-license your content for inclusion in The Perl 5 Wiki using this HOWTO, or join us for a chat on irc.freenode.net#PerlNet.

Official Perl 5 wiki discussion

From PerlNet

Jump to: navigation, search

Contents

Introduction

On Monday, July 9th 2007 Michael Schwern announced a new Perl 5 wiki hosted on The Perl Foundation servers. Since the announcement, there has been discussion with regards to the future of PerlNet and the new wiki.

This page should be considered an active discussion. If you add an opinion then please make sure you attribute it to yourself. You're welcome to add arguments, pros, cons, and discussions to any part of the text. It is a wiki, after all.

Recommendation: Dual-licensed contributions

For historical reasons, PerlNet requires all contributios to be made under the cc-by-sa license. The Perl 5 wiki uses the same license as Perl itself. You can indicate that you agree for your contributions to PerlNet to be licensed under the Perl 5 license by placing the following text on your user page:

 {{Perl5-license}}

This will allow your content to be freely transfered to The Perl 5 Wiki, under its preferred license.

A list of users who agree to dual-license their content can be found at Contributors_who_agree_to_the_Perl_5_license.

Other discussions

Possible merging

Should some or all of the content from PerlNet and The Perl 5 Wiki be merged? Merging of any form may require special approval from contributors if the new wiki contains a different license from the old.

You are strongly encouraged to leave your opinions and thoughts on this matter in the discussion below. Please sign your comments (using --~~~~) so they can be properly attributed.

Complete merge into PerlNet

Under this scenario all the content currently in the P5 wiki would be merged into PerlNet. The Perl 5 wiki may become a redirect to PerlNet.

  • This is never going to happen because the people who setup the Perl5 wiki will never do it. If they wanted to use PerlNet, they would have. -- Anonymous (193.111.87.20)

Pros

  • PerlNet already has established content, and additional infrastructure such as spam-removing bots and change-reporting IRC bots. PerlNet also presently has more material than The Perl 5 Wiki (citation needed), so there's less to move. --PJF 19:19, 9 July 2007 (EST)

Cons

  • The P5 wiki has a more memorable, and official sounding address Jarich 11:49, 10 July 2007 (EST)
  • People may view PerlNet as only being Australia based. Jarich 11:49, 10 July 2007 (EST)

Complete merge into The Perl 5 Wiki

Under this scenario, all content currently on PerlNet would be moved to The Perl 5 Wiki. perl.net.au will have redirects to the new site. --PJF 19:19, 9 July 2007 (EST)

Pros

  • The new wiki is given a fantastic start with new content and contributors. --PJF 19:19, 9 July 2007 (EST)

Cons

  • Local (AU/NZ) content is much less visible. --PJF 19:19, 9 July 2007 (EST)
  • More material needs to be moved, with more effort required for conversion. --PJF 19:19, 9 July 2007 (EST)
    • Licensing of moved material is a greater issue, due to the larger amount of it. --PJF 19:19, 9 July 2007 (EST)
  • External links need to be updated or redirects set in place. Jarich 11:49, 10 July 2007 (EST)
  • There's a huge chance that the Perl5 wiki will die out. The odds are good that within a couple of weeks, it will grow stale. -- Anonymous (193.111.87.20)
  • P5 uses the inferior SocialText engine. 09:33, 17 August 2008 (EST)

Non-regional merge

Under this scenario, non-regional contributions form PerlNet would be moved to The Perl 5 Wiki. Regional contributions would remain on PerlNet.

Pros

  • PerlNet still have front page space for upcoming meetings, regional jobs, etc -- Jarich 18:50, 9 July 2007 (EST)
  • Web searches from country specific addresses (eg google.com.au) will rank .au sites more prominent for searches for "Perl developer for hire" -- Jarich 18:50, 9 July 2007 (EST)

Cons

  • Although PerlNet is not particularly active and thus we are not generating more awareness of our regional groups from visitors to this page, I suspect that visitors here because of the regional material will no longer be encouraged to add their expertise to the non-regional content. Jarich 18:45, 9 July 2007 (EST)
  • Less cross-pollination between communities. PerlNet contributors are less likely to keep track of changes to TP5W changes, and vice-versa. This means less contribution cascades, and potentially less effective policing. --PJF 11:58, 10 July 2007 (EST)

No merge

Under this scenario, there would be no effort to bulk move content between wikis.

(Question -- can we have a layered WiKi to support this? Alec 19:16, 9 July 2007 (EST))

Pros

  • No licensing problems. --PJF 19:19, 9 July 2007 (EST)
  • Easy, no work to be done. --PJF 19:19, 9 July 2007 (EST)
  • You won't lose all your hard work when the new wiki goes under. -- Anonymous (193.111.87.20)

Cons

  • Possible forks in material. Content may be copied back and forth, and disparate versions created. --PJF 19:19, 9 July 2007 (EST)
  • Possible duplication in material. --PJF 19:19, 9 July 2007 (EST)
  • Fragmentation of communities. --PJF 19:19, 9 July 2007 (EST)


Wiki Available on pm.org

Under this scenario the pm.org web site will have a wiki available for every group. The regional group content - like upcoming events and talks - can then be put onto those wiki. One of the scenarios above about the non-group related and regional content still need to go ahead. e.g. merging the non-regional related content with perl5 wiki, and the regional staying on perlnet (example only)

Pros

  • Keeping identity is important. --Scottp 11 July 2007 (EST)
  • Melbourne.pm has wanted to keep identity within a site. Arguments above discuss exactly the same thing for keeping content within Australia - same arguments for keeping things within a group. Either we have an entire wiki for everyone, or the groups should have their own too --Scottp 11 July 2007 (EST)

Cons

  • There has been a small amount of work to get a wiki.pm.org going, but not a per group version yet. This can be done though (see Oddmuse wiki with automatic configuration). --Scottp 11 July 2007 (EST)
  • If we keep identity at each place, we will need a perl5 wiki, perl6 wiki (i.e. one per language); a set of regional Wikis and a set of PM Group wikis - this could be therefore difficult to maintain. --Scottp 11 July 2007 (EST)
  • More wikis will fragment the available contributors and policing pool even more. Lack of contributors and policing have been the major source of Perl wiki death so far. --PJF 10:36, 11 July 2007 (EST)
  • As far as I know, nobody is offering to do this. We have PerlNet, we have TP5W. At the moment talk of any other wikis is vapourware. --PJF 10:36, 11 July 2007 (EST)

Licensing issues

The Perl 5 wiki uses the same license as Perl 5 itself (GPL/Artistic). PerlNet uses the Creative Commons, sharealike attribution (cc-sa-by) license. It's expected that many contributors will be happy to dual-license.

Images on PerlNet are licensed for use on PerlNet only. However we don't have many images.

Personal tools