[Frugalware-devel] Frugalware newsletter maintainer

[Miklos Vajna]

On Mon, Nov 05, 2007 at 10:22:03AM +0000, Russell Dickenson <russelldickenson at gmail.com> wrote:
> Do I need a level of access I don't already have?

the newsletters are plain html files, so you can just send them here as
patches. here is what you need:

(for the first time)

git clone git://git.frugalware.org/pub/other/homepage-ng

cd homepage-ng

git config user.name "User Name"; git config user.email "foo at bar.com"

(later):

cd homepage-ng; git pull

- end of "getting the code" -

create frugalware/weeklynews/issue10.html

git add frugalware/weeklynews/issue10.html

git commit -m "newsletter issue 10"

git format-patch origin/master

and at this point you'll have a .patch file in the current directory,
you should send file here

if you later want to modify it, then you need:

git reset --soft HEAD^

<edit>, then again:

git add frugalware/weeklynews/issue10.html

(it may not be logical, you need git add every time you modified a file,
not just once, when you add a new file)

git commit -m "newsletter issue 10"

git format-patch origin/master

the resulting patch will be something like this:

http://git.frugalware.org/gitweb/gitweb.cgi?p=homepage-ng.git;a=commitdiff_plain;h=168c06860882c97295e51d40d22d5c4b4975ecc3

and

http://git.frugalware.org/gitweb/gitweb.cgi?p=homepage-ng.git;a=commitdiff_plain;h=77719d10e2c5fff3023c7b31250bdd0230ba3519

(i describe this because then later if you get an account, all the
diference will be that you need git push instead of "format-patch and
email". and of course it's easy for us if we can just apply your patch
:) )

> To where/whom should I submit my newsletter content?  Who will review
> and approve what I write?

IIRC, Alex did a new issue on every two weeks. so something like could
work IMHO:

1) you post the patch here 1-2 days before the planned release (it used
to be relased on Sundays or Saturdays), anybody can claim

2) if there is something wrong with it, then we can claim

3) i (or somebody else) can apply it if there are no problems with it. i
suppose there may be smaller problems with the first releases, then the
usual practice could be that "you post, we wait for a day, then we push
it out as it's ok"

a strongly personal opinion: the devel list is public, if somebody is
interested, then he/she can see what we are working on, but it's nicer
if we talk in the newsletter about what we already did :) (or at least
we have a test-able version). for example it may worth a note, that we
knows that xorg-7.3 is out, and if somebody wants, then he/she can use
the http://ftp.frugalware.org/pub/other/people/krix/xorg73/ repo, but
he/she should be warned, it's not an accident that we haven't merged it
yet to current

to see what has been done since a given version, you need to run
'repoman upd' then:

cd /var/fst/current

'git log 0.7..'

thanks :)

- VMiklos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20071105/091419c4/attachment.bin