Drupal

Drupal isn't really a wiki, it's a CMS. That distinction is important here, because it means we can't do anything besides basic HTML. ~spot

I realized you would say this right after I hit send. I was thinking there was a drupal wiki module. But the only thing I see is: http://www.interestingto.me.uk/DrupalWikiModule I should have left

Fair enough. :) I'm still hopeful that there is some wiki intelligence in addition to Drupal already present, and if not, I can make the case for us to move to mediawiki. ;) ~tom

* Tom spot Callaway <tcallawa@...> [2010-08-24 21:09]: Bob's right. We're using Drupal and the Drupal wiki module. What functionality do you need that's currently not there? -- Martin

Well, there are a few things: 1. New page creation is really awkward. 2. There is no native wiki link syntax, so I would end up making a lot of long URLs that aren't useful. 3. There is no native

Attached is the agenda. I've called out the logistical info separately. Note: We are in flux with dial in numbers, so please check every time. and Note: I am experimenting with using the Web log in to

Forgot attachment.

I won't be attending this week, due to a conflict. See you at the next meeting. -- Marshall

Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF Current status: - need to focus on goals for next 3 months - SPDX.org rollout, shadows fossbazaar.org for data. - mail list transfering to

Some people have been asking for it. We finally have a pre-release. You can download it from: http://turingmachine.org/~dmg/temp/ninka-1.0-pre1.tar.bz2 (licensed AGPLv3) I have discussed with Kate

these the licenses we currently identify. Look particularly at the BSDs and MIts. Some are not licenses but their exception statements. I have the feeling that these cover around 75-86% of files in

Thanks Daniel. As the reference page for each license and its header emerge - cross checking against this is going to be useful. Hmm, am a little concerned about putting some of them into the

I agree, not all are licenses. Exceptions, for example, are treated as a license, but to make sense, they have to accompany a real one. What I recommend people do, if really interested, is look at

kate> In particular the BSD and MIT varients look worrisome. Any kate> volunteers to review the details there and make some kate> recommendations? If SPDX is interested, look at the data for

Hi Kate et al, As we discussed on the call a few times, I think having this amazing list of license in one place is a great asset to the community and I believe will help reduce license

Jeff Luszcz twisted the bytes to say: Jeff> Hi Kate et al, As we discussed on the call a few times, I think having this amazing list of license in one place is a great asset to the community

Once a license is "approved" and placed in the repo it should be immutable. That way there is no chance of the text changing once the license name is in use. To prevent links going defunct we could

I agree. Also: If an spdx document is supposed to contain all the license texts, isn't there a danger that we end up documenting 10 KB of source code with 1 MB of license texts? (Yes I know, if there

Hi, here is some feedback I received recently - I'm not sure how much of it is (still) relevant. Ciaran ============================================================================== Page 4: 1.1