Redhog Pad

[Brian Herman]

Is redhog pad ready to be merged to the main github repository?
Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[Dana Chandler]

I'm not sure  know whatyou nean by redhog pad? Are you referring to reshog's comments about the diffs? I don't think anyone has actually done anything on that yet.

Best,

Dana

Sent from my iPhone (forgive all typos)

[Brian Herman]

http://github.com/redhog/pad

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[John McLear]

most of it is merged...  he means the v1.0.0 to v1.0.1 bits from the plugin framework I guess..  Yes that is ready to merge afaik, although we need to run throgh testing

please grab from redhog/pad and test a deployment w/ apt then test the plugin framework

documentation was v flakey last time i tested, should be fine now..

kudos to joe and egil for getting it done

[Brian Herman]

Is there a way to do a mysql dump of the documentation server so I can search the database better.
I know you can do it through google but I am just lazy.
I would be willing to compile all of the information into a pdf.
I am doing that anyway for my job.

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[RedHog]

http://etherpad.org/dumps/doc/doc_etherpad_org%20Wed%20Jun%2023%2001:15:14%20CEST%202010.sql.gz

Please note that this file is rather big, so don't download it several
times / if you don't actually need it.

As for compiling information, it'd be really really useful if we could
get http://code.google.com/p/jsdoc-toolkit/ working with etherpad.

[Brian Herman]

Only will download it once!
WOW YOU ARE AMAZING!
You work so fast!

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[Brian Herman]

Well it is publicly available information.
Anyone could create a screen scraping script.
Google indexes our information already in their cache.
That is how I search the documentation.
I'll check if anyone put a copyright in.
But if no one objects.... I wont waste my time.
But it is a valid argument.
We should talk at the next meeting what our documentation should be under.
I suggest the

The GNU Lesser General Public License

The GNU Lesser General Public License is used by a few (not by any means all) GNU libraries. The latest version is version 3.

• The GNU Lesser General Public License text is available in these formats: HTML, plain text, Docbook, and Texinfo. These documents are not formatted for standalone publishing, and are intended to be included in another document.
• Why you shouldn't use the Lesser GPL for your next library
• Older versions of the GNU LGPL

Since the database is plain text..
But the community should decide.

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

On Thu, Jun 24, 2010 at 9:36 AM, John McLear <john...@gmail.com> wrote:

Wow I didn't expect to see this online :o

I guess there are no privacy/security concerns dumping this?

[John McLear]

I'm not concerned about the content itself, it's more about if it contains any IPS or so in teh logs.

[Brian Herman]

IPS?

?_?

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[Daniel Reeves]

IP addresses.

[Brian Herman]

Doh!

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[John McLear]

Lol

On Jun 25, 2010 11:43 AM, "Brian Herman" <brian...@gmail.com> wrote:

Doh!

Thanks, Brian Herman brianjherman.com Research Assistant University Of Illinois at Chicago brianh...

On Thu, Jun 24, 2010 at 1:51 PM, Daniel Reeves <dre...@gmail.com> wrote: > > IP addresses. > > On T...

[Per Andersson]

On Thu, Jun 24, 2010 at 5:42 PM, Brian Herman <brian...@gmail.com> wrote:
> We should talk at the next meeting what our documentation should be under.
> I suggest the
>
> The GNU Lesser General Public License

Why LGPL docs?

I suggest either using GPL3+, GFDL or the same license as EtherPad (Apache 2.0).

> Why you shouldn't use the Lesser GPL for your next library

Do you put forward this as an argument why LGPL should be used?

-- Per

[Brian Herman]

It was just the first one I thought of I just wanted there to be some discussion for it.
Sorry about the copypasta.

Thanks,
Brian Herman

brianjherman.com
Research Assistant
University Of Illinois at Chicago
brian...@acm.org
Consultant
University of Chicago

[Joe Corneli]

I personally like CC Zero for documentation.

Whatever the license it would be nice to rally once again
for the creation of an Etherpad Manual. I tried
once before to get the doc.etherpad.org stuff
organized, but I forgot to tag the pages I created
as #public #writable and currently they are lost
somewhere in the database.

It may also be best just to use jsdoc as discussed
in the meeting, in which case, yeah, the license
for the docs would (by default anyway) be the
same as Etherpad's license.