Phil, I believe that the entire LOPSA content philosophy has been "thanks for sharing your content, we really appreciate your work" combined with "we hope that you will post at LOPSA to foster our community" with a side order of "we're happy to host your content, esp if you don't have a place to host it, or if we can help it get more visibilty".
I absolutely agree with your comments about data migration. Making content that was perfectly fine into something that isn't is well... bad. I personally would like to see the issue resolved so that your content could remain at LOPSA.org. I wonder if this has happened to other contributors? Having interesting content that leads to LOPSA's site is important for helping prospective new members find us as well as fulfilling LOPSA's educational and community missions. My *personal* opinion is that moving the content to your blog is fine, and it would be nice if you left a "content has moved" link behind, and perhaps added "originally posted at LOPSA.org" (with a link to the main site) to the content's new home. I seem to recall that ownership of member-created content at LOPSA.org was a topic of discussion when we launched the site. *IF* I recall correctly, the sense of the Board was that we wanted all copyrights and ownership to remain with the creator and explicitly rejected anything that would have LOPSA claim any rights to member created content. I remember there was a discussion that we might request that members give LOPSA an exclusive on the material for a set period of time, but that was *before* we added the member blogs. I think that was going to be for articles that were created for publication at LOPSA.org, definitely not for blogs. Hopefully I haven't muddied the waters too much, --tep _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
