Seeking Maintainers for Showdown
coreyti opened this issue · comments
With apologies, I've long been unable to stay up with maintaining Showdown on Github. As such, I've moved the repository to the "showdownjs" organization. I'm seeking maintainers to take over ownership of that organization and the Showdown project.
Please respond here if interested.
@coreyti now that repo as been moved to organization, I'm in!
@pdeschen great! Sorry for the long delay... I've added you to the organization's owners.
@coreyti I am also interested.
@coreyti, I'm also interested. Been using Showdown for a while, fixing some
bugs and adding support for some frameworks, such as AngularJS, in my local
repo.
Estevão Soares dos Santos
2014-10-11 18:49 GMT+01:00 Corey Innis notifications@github.com:
Hi @sirakoff https://github.com/sirakoff, thanks for raising your hand.
I'm glad to hear of your interest. I feel somewhat inclined to see if any
of the other previous contributors, such as @tstone
https://github.com/tstone and @remy https://github.com/remy, would
want to form the core. @pdeschen https://github.com/pdeschen, thoughts?—
Reply to this email directly or view it on GitHub
#114 (comment).
@tivie just added you.
@coreyti Thanks. I have a couple of bug fixes and features (such as AngularJS integration) that should be ready to push. This repo only has a master branch though. What is the model you guys adopt? The standard Feature/Hotfix -> Develop -> Master -> Release? Or Fork(and branch) -> Push request?
@tivie I'm interested in your AngularJS integration, when do you think you'll be able to publish it on a dev branch?
@florenthobein It's already available in the feature branch Angular_Integration. I haven't merged it in the development branch yet because I'm waiting for some feedback from @coreyti or @pdeschen.
Regardless, you can download the source file ng-angular.js and include it in your page after angular and showdown.
Some feedback and testing is appreciated =)
@tivie Is there a PR open for your work to date? Love to help you refactor a little...
👍 would love to help
I've just pushed a very very alpha version of the showdown refactoring. Love if you could have a look.
@tivie would you mind opening a PR? I'll give it a shot at reviewing
I'd like to help out as well- specifically on the AngularJs integration side.
I'd also be happy to help migrating from grunt to gulp(v4.0 when its released) task automation.
@SyntaxRules I'm fine with you coming aboard, if @pdeschen and @coreyti agree.
Regarding migrating to gulp, my question is: why?! The best thing would be dropping grunt (or gulp, or brocolli, or whatever) altogether and switch to pure NPM based tasks. =P
@tivie Thanks. An advantage of gulp over grunt is speed. Its hard for me to say how much of a speed up you would get by migrating (if any) because I don't know all the specifics of how this project uses grunt.
I can see the argument for just using npm modules and I totaly agree this works out well for simple projects. So maybe that applies here.
switch to pure NPM based tasks
Not enough power, no incremental rebuilds etc. etc.
After I used Showdown on my own project I've written a Dev.to article about extending it:
https://dev.to/gtanyware/how-to-customize-markdown-4geo
Am also interested.