On Wed, 2011-12-14 at 18:34 +0100, Christian PERRIER wrote: > (CC'ing you just in case, though I think you're subscribed to pkg-fonts-devel) > > Quoting Martin Erik Werner (martinerikwerner@gmail.com): > > Dear mentors and pkg-fontsers, > > > > I am looking for a sponsor for my package "fonts-play". > > > I added it to my TODO list as I'm now sponsoring most of the font > packages maintained under the team's umbrella. > > Please feel free to ping me in case it falls under the pile...:) > > Interesting that you used git for packaging. I think it opens the > opportunity for those in the team who would like to use it rather than > SVN (which is used for other packages maintained by pkg-fonts), to > switch to git. > > Help in importing the current SVN repo in git would be > appreciated. Most font packages in pkg-fonts SVN use an > svn-buildpackage style layout. > > I noticed that a couple of other font packages were already contained in git so I'm not sure I'm the first one here... I don't have much experience in git->svn migration, but I'm happy to help out where I can. As far as I know, it seems common practice to keep separate packages in separate git repositories, would this be the intention for pkg-fonts as well in the case of migration? Also, there's quite a few differing workflow setups with git, I'm using a standard git-buildpackage style, with quilt slapped on top without integration, I'm guessing opinions differ here ;) As mentioned, creating a separate googlefontdirectory-tools(name?) with the capability to build gfd fonts from source, is something I'd like to do in the future, hopefully some current gfd packages might find it useful. -- Martin Erik Werner <martinerikwerner@gmail.com>
Attachment:
signature.asc
Description: This is a digitally signed message part