Thread: [Mactextoolbox-talk] BibDesk participation
Status: Planning
Brought to you by:
jlaurens
Menu
▾
▴
mactextoolbox-talk
|
From: Michael M. <mic...@gm...> - 2005-06-22 01:32:15
|
Hi - I saw Maarten's posting on the macosx-tex list and the website he's set up - nice job! We should probably add BibDesk to the list of participating projects, as soon as I hear what exactly that means. I'm already on this list, and I've cc'd the bibdesk developer list on this email to see if anyone else there wants to join up. You've got my permission to use the BibDesk icon graphic on the bibdesk.sf.net site for the participating projects page. Let me know what else is involved, and thanks for the work organizing this. -mike --=20 Michael McCracken UCSD CSE PhD Student San Diego Supercomputer Center http://www.cse.ucsd.edu/~mmccrack/ |
|
From: Maarten S. <maa...@xs...> - 2005-06-22 22:04:42
|
On 22 Jun 2005, at 3:32, Michael McCracken wrote:
> Hi - I saw Maarten's posting on the macosx-tex list and the website
> he's set up - nice job!
\begin{blush}
Well, eh, thanks!
\end{blush}
> We should probably add BibDesk to the list of participating projects,
> as soon as I hear what exactly that means.
At the moment I have no idea where we'll end up with the project. The
main idea is that developers of the various tools join forces, to
make sure that common code is implemented using the same (debugged)
code. More importantly perhaps: to develop a common user interface
terminology, to increase consistency between the various tools.
The main aim is communication and collaboration. And to encourage new
developers to contribute to existing tools, rather than starting new
projects - the situation with the equation editors is a prime example
of what we'd like to avoid. Of course when an idea for a radically
new tools comes up, a new project can be started.
Participation of a project means that some developers of that project
will listen to the mailing list, and occationally post commentary,
requests for help, etc. Articles on specific issues are appreciated
(how to add TeX specific AppleScript support, an overview of the code
in your project, so that it becomes easier for others to reuse,
please surprise me).
To spread the word about this project, I'd like to steal some
advertising space in your documentation, the about box or your web-
page - under the assumption that developers embarking on a new
project will do some research, and come across existing tools, which
will lead them to either your project or the umbrella toolbox
project. How these links will work out eventually, I don't know yet,
and I'm not planning on playing a cop on the issue: add a reference
to your own web-location in the about box, and add the toolbox logo
(after the contest for a good logo is finished) to your own web-page.
> You've got my permission to use the BibDesk icon graphic on the
> bibdesk.sf.net site for the
> participating projects page.
I would like to have your description as well: just a short
description to add to the list (what is BibDesk, why should you use
it, and what development tasks could use some extra hands).
> Let me know what else is involved, and thanks for the work
> organizing this.
At the moment: not much: I lack the time right now. I'll add new
articles as I receive them, and the mailing list will go forward.
I'll probably add some of my own scripts to the file download section
or at least to the CVS repository. Private advice on how to maintain
a sourceforge project is appreciated.
Maarten
|
|
From: Maxwell, A. R <ada...@pn...> - 2005-06-23 18:43:55
|
On Jun 22, 2005, at 15:04, Maarten Sneep wrote: >> Let me know what else is involved, and thanks for the work =20 >> organizing this. >> > > At the moment: not much: I lack the time right now. I'll add new =20 > articles as I receive them, and the mailing list will go forward. Maybe Mike's research on Apple Help writing would be useful for an =20 article :). > I'll probably add some of my own scripts to the file download =20 > section or at least to the CVS repository. Private advice on how to =20= > maintain a sourceforge project is appreciated. Or perhaps public advice on this? Mike and J=E9r=F4me have been =20 maintaining sourceforge projects longer than the rest of us, and I'd =20 be interested in any tips as well. regards, Adam= |
|
From: Michael M. <mic...@gm...> - 2005-06-23 19:48:28
|
On 6/23/05, Maxwell, Adam R <ada...@pn...> wrote: >=20 > On Jun 22, 2005, at 15:04, Maarten Sneep wrote: >=20 > >> Let me know what else is involved, and thanks for the work > >> organizing this. > >> > > > > At the moment: not much: I lack the time right now. I'll add new > > articles as I receive them, and the mailing list will go forward. >=20 > Maybe Mike's research on Apple Help writing would be useful for an > article :). Good idea - we could share what we've learned so far, and considering that= =20 the tools we ended up with are similar to tex and at least open-source, it might make sense to share them with the community. For reference, I started out here: http://michael-mccracken.net/blog/blosxom.pl/computers/mac/programming/sing= leSourceDocs.html and made a bunch of posts to bibdesk-dev with further info. If you like, I could turn those various posts into a single article aimed at the toolbox's audience. =20 > > I'll probably add some of my own scripts to the file download > > section or at least to the CVS repository. Private advice on how to > > maintain a sourceforge project is appreciated. >=20 > Or perhaps public advice on this? Mike and J=E9r=F4me have been > maintaining sourceforge projects longer than the rest of us, and I'd > be interested in any tips as well. Hmm, tips - well, for starters I'd suggest making sure you disable anything you aren't planning to use - the screenshots archive is particularly useless, IMHO, and if you have lists you may not also want forums. Another tip is that anything you can do to get automatic notifications instead of having to revisit the website is worth your time to set up. Make sure you have new tracker items send email somewhere you check - BibDesk has -bugs and -rfes mailing lists that catch all new items, even if they're not assigned to someone. If you don't do this and nobody assigns anyone to a new item, that item falls through the cracks until the next time you go browse the tracker's web interface... Also, I have ssh-keys set up for my sourceforge account, and thank god. I would surely hate life if I had to type in my password every time I used CVS for BibDesk... The info about that is here:=20 http://sourceforge.net/docman/display_doc.php?docid=3D3088&group_id=3D1 I'll try to think of others, but that's all I've got for now. -mike --=20 Michael McCracken UCSD CSE PhD Student San Diego Supercomputer Center http://www.cse.ucsd.edu/~mmccrack/ |
|
From: Maarten S. <maa...@xs...> - 2005-06-23 21:04:38
|
On 23 Jun 2005, at 21:48, Michael McCracken wrote: > On 6/23/05, Maxwell, Adam R <ada...@pn...> wrote: > >> Maybe Mike's research on Apple Help writing would be useful for an >> article :). > > Good idea - we could share what we've learned so far, and =20 > considering that > the tools we ended up with are similar to tex and at least > open-source, it might make sense to share them with the community. > > For reference, I started out here: > http://michael-mccracken.net/blog/blosxom.pl/computers/mac/=20 > programming/singleSourceDocs.html > and made a bunch of posts to bibdesk-dev with further info. > > If you like, I could turn those various posts into a single article > aimed at the toolbox's audience. That would be really nice. There are some templates available from =20 the articles page, if you want those. >>> I'll probably add some of my own scripts to the file download >>> section or at least to the CVS repository. Private advice on how to >>> maintain a sourceforge project is appreciated. >> >> Or perhaps public advice on this? Mike and J=E9r=F4me have been >> maintaining sourceforge projects longer than the rest of us, and I'd >> be interested in any tips as well. > > Hmm, tips - well, for starters I'd suggest making sure you disable > anything you aren't planning to use - the screenshots archive is > particularly useless, IMHO, and if you have lists you may not also > want forums. > > Another tip is that anything you can do to get automatic notifications > instead of having to revisit the website is worth your time to set up. > Make sure you have new tracker items send email somewhere you check - > BibDesk has -bugs and -rfes mailing lists that catch all new items, > even if they're not assigned to someone. If you don't do this and > nobody assigns anyone to a new item, that item falls through the > cracks until the next time you go browse the tracker's web > interface... > > Also, I have ssh-keys set up for my sourceforge account, and thank > god. I would surely hate life if I had to type in my password every > time I used CVS for BibDesk... > The info about that is here: > http://sourceforge.net/docman/display_doc.php?docid=3D3088&group_id=3D1 > > I'll try to think of others, but that's all I've got for now. Thanks for this, and thanks for the text on BibDesk. I'll add the =20 discription some time after the weekend. Maarten= |
|
From: Michael M. <mic...@gm...> - 2005-06-23 19:58:49
|
> I would like to have your description as well: just a short > description to add to the list (what is BibDesk, why should you use > it, and what development tasks could use some extra hands). I suggest just using this from the http://bibdesk.sourceforge.net website: BibDesk is a graphical BibTeX-bibliography manager for Mac OS X. BibDesk is designed to help organize and use bibliographic databases in BibTeX .bib format. In addition to manual typing, BibDesk lets you drag & drop or cut & paste .bib files into the bibliographic database and automatically opens files downloaded from PubMed. BibDesk also keeps track of electronic copies of literature on your computer and allows for searching your database through several keys. And as far as what development tasks could use extra hands, for now I'd say the following, although if we get a lot of response we might put a list of projects up on the wiki: BibDesk is an active project that makes full use of its bug and feature request trackers. If you want to help out, find or create a feature request you want to implement or a bug you want to fix, join the developer mailing list[1] and talk to us! Non-coding help that is always appreciated is translation, web site and wiki improvements, documentation, testing, etc... [1]:http://lists.sourceforge.net/lists/listinfo/bibdesk-develop How's that sound? -mike --=20 Michael McCracken UCSD CSE PhD Student San Diego Supercomputer Center http://www.cse.ucsd.edu/~mmccrack/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X