[pmwiki-users] Proposed change to pmwiki.php: Markup_e
xraysmalevich at gmail.com
Thu Feb 13 14:40:06 CST 2014
I just double-checked; the "Issues" section of a GitHub repo can be
deactivated, so the repo's reademe.md file could direct issues to go to
The drawback, though, is that Issues and pull-requests are well-integrated.
Another bonus of GitHub -- each repo comes with its own wiki, a CMS-engine
for rapid page creation!
(Which can also be turned off.)
<http://goog_2112721603>Interference Patterns (a
Sent from somewhere in the Cloud
(hearthrug, by the fender)
On Thu, Feb 13, 2014 at 3:23 PM, Petko Yotov <5ko at 5ko.fr> wrote:
> michael paulukonis writes:
>> Two potential issues with moving to github:
>> 1) the standard is to put issues onto github; this would mean there is
>> both github issues and PITS issues.
> I've said this before, I do like PITS, this is the WikiWay, it is easy to
> demonstrate a problem, to link to the documentation etc.
> I have a client who migrated from Google Code to a slightly customized
> version of PITS, right after I revamped the interface in 2009. They are
> still using it daily.
> OTOH there may be good reasons to move to a different issue tracker.
> One great thing in pmwiki.org/PITS is that everything, the wiki, the
> documentation, the cookbook and PITS are on the same wiki, and there are a
> few people monitoring AllRecentChanges and, more often than I expect, help
> me with the mainainance and reply to questions - for which I'm really
> grateful. If we move to a different issue tracker, I'm afraid we'll have to
> put more efforts in another website to monitor.
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pmwiki-users