Re: How to begin helping in Pybliographer development

>
>
> Great, you're of course welcome !


Thank you!


The devel version is very very different from the stable--1.2, which is
> probably the one you're interested in:
>
> - 1.2 is the version with the UI as you know it
>
> - 1.3 is mostly (as of today) a framework on top of which no actual
> end-user application is packaged right now. It contains lots of new
> features, but not all of the old ones, so it is not ready for prime
> time.

[...]

So I suggest you check out the pybliographer--stable--1.2 branch.


Well, I'm sure interested in *using* the stable branch (and bugfixing it).
But I would like also to help with 1.3 if possible, in the future. I
understand that it's a still scratchy work-in-progress, so I will first try
to understand and be familiar with the stable branch.

I'm thinking of joining your project for two (distant) reasons. First,
because I like to code, I like python and I'd love a significant project
where I can do some help. Second, I'd like to improve Pybliographer to use
it actually. It's a nice instrument, but unluckly we don't use much LaTeX /
LyX in our molecular biology lab (I'd love to use it, I have used it for my
graduate thesis, but there are even journals that *refuse* LaTeX, one of
these is -whoa!- Nature. Moreover my boss doesn't even know what LaTeX is,
let alone convincing him to switch). I am, lonely Linux user in a
Windows-centric environment, unluckly forced to use .doc/.rtf formats (and
OpenOffice deals with them just fine) and EndNote archives (that's where
pain begins).

I am therefore particulary interested in adding/improving OpenOffice
integration (I have seen there's a project about it) and EndNote
compatibility. I'd like to have any info about the development of these
features.

>
> The ,,index file is an artifact of tla, it is not part of pyblio itself.


Yes, I figured it.

(as of today, the best arch client is called baz and is available from
> <http://bazaar.canonical.com/>, so I suggest you to use it instead of
> plain tla if possible. The two can be used on the same archive, so no
> worry. I need to update the website BTW)


I'll give it a try.

You can also join the freshly created pybliographer-devel mailing list.


I'll do it :)
 This guide is indeed theoretic, as it should serve as a guideline for

> more radical changes which were not yet properly started, due to a lack
> of resources.


Ok. I'll have a deeper look in it :)

> Yes, it's the official list. You only see old bugs because the others

> are closed :-)


So what's on the list isn't still closed ;-) ?

If you have the possiblity to join, there is a weekly IRC meeting every
> wednesday at 21:00 CET, channel #pyblio on irc.freenode.net<http://irc.freenode.net>
> .


Ok, I'll try to remember it.

In any case, you are more than welcome to ask loads of questions on the
> mailing list.


That's what I'm already doing :)

Massimo