https://wiki.blender.jp/index.php?action=history&feed=atom&title=%E5%88%A9%E7%94%A8%E8%80%85%3AMindrones%2FWiki%2FProposals%2F2009%2FWorkflow%2FDevelop 2026-08-01T12:37:06Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Mindrones/Wiki/Proposals/2009/Workflow/Develop&diff=90711&oldid=prev 2018-06-28T18:43:27Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 18:43時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Mindrones/Wiki/Proposals/2009/Workflow/Develop&diff=90710&oldid=prev 2010-03-06T15:50:00Z

<p>moved <a href="/%E5%88%A9%E7%94%A8%E8%80%85:Mindrones/blender-wiki/proposal/workflow/develop" class="mw-redirect" title="利用者:Mindrones/blender-wiki/proposal/workflow/develop">User:Mindrones/blender-wiki/proposal/workflow/develop</a> to <a href="/%E5%88%A9%E7%94%A8%E8%80%85:Mindrones/Wiki/Proposals/2009/Workflow/Develop" title="利用者:Mindrones/Wiki/Proposals/2009/Workflow/Develop">User:Mindrones/Wiki/Proposals/2009/Workflow/Develop</a></p> <p><b>新規ページ</b></p><div>= Using wiki for development =<br /> &lt;br&gt;<br /> <br /> == Feature requests ==<br /> ----<br /> * Feature requests from users<br /> * Feature a developer wants to develop<br /> * Companies paying a developer for features they need<br /> <br /> === Feature requests Tracker ===<br /> <br /> * Feature requests tracker (possibly pubblic)<br /> * Folders with Manual structure<br /> * Ubuntu uses a [https://help.launchpad.net/Blueprint blueprint system] for handling<br /> specifications for new features<br /> <br /> <br /> == Discussion ==<br /> ----<br /> * Discussion on '''wiki'''<br /> * Discussion on blenderartists<br /> * Discussion on IRC<br /> <br /> == Coding and committing ==<br /> ----<br /> Then the developer: <br /> <br /> *make a unique patch, post it in the tracker and ask other developers/users to revision, and some day his patch goes into trunk, OR<br /> *open an svn branch and start committing patches to svn, and some day his branch is merged to trunk <br /> *in any case he could explain ideas and functionalities in func-board mailing list, in the patch tracker itself, or '''wiki'''<br /> <br /> === Testing / discussion ===<br /> ----<br /> People compile and try the patch/svn-version and give some feedback in '''wiki''', chat, trackers, or mailing lists&lt;br&gt; <br /> <br /> === svn log commits tags ===<br /> ----<br /> At this point we can have one (in case of a patch) or more commits in svn, but release might happen way after this commit.&lt;br&gt;<br /> How to remember this has happened? As for now we have svn log, which has to be read and catalogued &quot;by hand&quot;.&lt;br&gt;<br /> Proposal: devs put a newline in their committ like:<br /> &lt;pre&gt;WIKI: mesh, undo&lt;/pre&gt;<br /> and this can be parsed to add a special page in wiki with all the svn logs that contain those TAGS. In case we want to see pages related to more than 1 word, we can use the DynamicPageList alredy installed on Blender wiki.<br /> <br /> See this section about [[#Categories_and_tags|categories and tags in wiki]].<br /> <br /> &lt;pre&gt;<br /> &lt;bebraw&gt;I thought about the commit tagging problem (how to know which tags to use<br /> in the first place). There probably has to be some<br /> page that lists all the available tags. This way people actually know<br /> which tags they can use. Even better there could be a specific<br /> application that would make tagging easier (the app would just help to<br /> compose the commit message and help enforce commit rules (header,<br /> message content, tags etc.)). As people make mistakes (forget to tag,<br /> use wrong tag, etc.) there should be some way to modify the tag<br /> information related to commits later (this is probably a system<br /> separate from commit log one and is then combined to the original<br /> commits somehow?).<br /> &lt;/pre&gt;<br /> <br /> The next section might offer a good answer to these thoughts?<br /> <br /> ==== Blogging via mail ====<br /> <br /> Some blogging or photo sharing sites let you post blogs (and tag them) via mail:<br /> * Flickr: [http://www.flickr.com/help/photos/#140 How can I add tags when I upload via email or my phone?]<br /> * Wordpress: [http://codex.wordpress.org/Blog_by_Email Post to your blog using email]<br /> * Blogger: [http://help.blogger.com/bin/answer.py?hl=en&amp;answer=41452 How do I post via email?]<br /> * Posterous: [http://blog.posterous.com/posterous-launches-easy-post-t Posterous launches easy post tagging via email]<br /> <br /> Since [http://www.yofrankie.org/ Apricot's blog] uses Wordpress, which has an [http://www.yofrankie.org/xmlrpc.php xmlrpc interface], it lets you blog via mail! :)<br /> Using the same (already known) software, we could setup a blog just for publishing svn logs and we would have a ready-made system for let users manage tags :)&lt;br&gt; It would be a matter of set svn to send mails to blog mail (together with usual mails to bf-blender-cvs list).&lt;br&gt;<br /> Then with a [[User:Mindrones/blender-wiki/proposal/reference#Retrieving_categories_and_tags_via_python.2Fxmlrpc|python script]] we could retrieve the tags and periodically update a wiki &quot;svnlog&quot; page (with Categories as chapters and tags as sub-chapters), or many svnlog pages divided per categories and tags. See [[User:Mindrones/blender-wiki/proposal/reference#Blogging_via_mail|this reference]].<br /> <br /> [[User_talk:Mindrones/blender-wiki/proposal/workflow#Blogging_via_mail|Discussion]]</div>

wiki>Mindrones