On Fri, May 15, 2015, at 06:06 PM, Alekseyev, Vsevolod (NIH/NIAID) [E] wrote: > Do you think it's preferable to submit several smaller patches as > functionality becomes available, or one big one at the end? >
I think it's preferable to submit what would be a coherent feature set. If there are additional features you want to add, you can submit patches later. On Fri, May 15, 2015, at 06:27 PM, Alekseyev, Vsevolod (NIH/NIAID) [E] wrote: > Also, do you guys have a policy regarding real names vs. workgroups? > > I did this as a part of my job, and don't want to claim credit as an > individual, so I'd like to register a group account for the team I'm a > part of. The name won't be mine, but the e-mail address is real, and mail > would reach me. > > However, I know some open source projects don't like group accounts... > I don't think group accounts are the solution to the problem. If a single account is shared by many people, it can cause confusion as to who the actual authors of comments are. For groups, ideally there would be a way to manage organizations such that people would still register single user accounts, but then can join an organization. I'm not sure if the Blender's source control manager supports this. For your problem in particular, I think you just want to attribute credit to NIH. Maybe it's better to register as yourself and in the author argument of bl_info, say "[your name], as part of NIH 3D Print Exchange". Or under the GPL license block, make another comment block thanking NIH. These are my opinions, and others may differ. Good luck, Jenny > ________________________________ > From: Jenny [[email protected]] > Sent: Friday, May 15, 2015 6:19 PM > To: [email protected] > Subject: Re: [Bf-python] Got X3D import fixes > > Hi Alekseyev, > > Could you submit it to https://developer.blender.org? There's a "Submit > Addon" section. > It's easier to track comments there instead of this mailing list, and > ultimately it would get merged in from there. > > In addition, would you also mind creating a Git patch file for these > changes? > > Thanks, > Jenny > > > > On Fri, May 15, 2015, at 02:21 PM, Daniel Monteiro Basso wrote: > Hi Alekseyev, > > On Fri, May 15, 2015 at 8:55 PM, Alekseyev, Vsevolod (NIH/NIAID) [E] > <[email protected]<mailto:[email protected]>> wrote: > It's called import_x3d.py , and it should go into C:\Program > Files\Blender Foundation\Blender\%VERSION%\scripts\addons\io_scene_x3d > (on Windows) or into /usr/local/blender-$VERSION/$VERSION > /scripts/addons/io_scene_x3d (on Linux). Before replacing the file, > *PLEASE SAVE THE ORIGINAL*. > > Note that on Linux you should not overwrite the system's Blender files, > but install locally for the user in /home/<user > name>/.config/blender/<version, e.g. 2.74>/scripts/addons. The user's > version takes precedence over the system-wide installation of Blender. > > Cheers, > Daniel > _______________________________________________ > Bf-python mailing list > [email protected]<mailto:[email protected]> > http://lists.blender.org/mailman/listinfo/bf-python > > _______________________________________________ > Bf-python mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-python _______________________________________________ Bf-python mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-python
