Project returns to active status

[mrichar1]

Hi,

I've just found docson, and think it could be a useful tool for me - however I notice that there are a relatively high number of outstanding PRs and issues, and a high number of forks which seem to be ahead of this project.

I'm wondering if this project is no longer being supported? If so, are there any active forks which could be considered as a replacement for this one? Or could this project be moved to being a community-run one?

[lbovet]

Indeed, I had not the resource to steward this project further as I would have liked to do. PRs have accumulated and different forks solved the same issues and present incompatible changes. I agree that everyone could benefit from a community-based project, assuming that there is enough homogeneity in the features requested by the community. That said, it will need a team, a lead or at least a steward for this community. Anyone interested?

[yanick]

@lbovet Fwiw, I'd be interested in helping merging the PRs in and keeping the project alive.

[lbovet]

Great! Welcome Yanick! I gave you push access, so you can work asap on the project. I let you full control on actions there. We can consider in a later step to move the project into a dedicated organization.

[yanick]

Heh. That was easy. Thanks! :-)

@lbovet Do you have any protocol we should follow in mind (having you veto PRs that can be merged to master, etc), or should I merge things to master as I think it makes sense, and poke you went I think a release is ready?

[lbovet]

Yes, do it like you feel. You can merge the open PRs on a branch of yours and then merge this on master when ready to release (via a self-PR). This way, it is easy to have a look at all changes at once. I do not want to veto or slow you down, just have the possiblity to easily follow the upcoming history you are about to write :) Happy merging!

On Fri, Feb 2, 2018 at 5:47 PM Yanick Champoux notifications@github.com wrote:

Heh. That was easy. Thanks! :-)

@lbovet https://github.com/lbovet Do you have any protocol we should follow in mind (having you veto PRs that can be merged to master, etc), or should I merge things to master as I think it makes sense, and poke you went I think a release is ready?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lbovet/docson/issues/56#issuecomment-362615802, or mute the thread https://github.com/notifications/unsubscribe-auth/AAqPnHTa_TvqtuwidkfbjAtWdJ6zSRXRks5tQygqgaJpZM4RDpcx .

[rom1504]

If I could advise something, it might be interesting to have a look at my PR about putting docson on npm. Npm is the way front end is done these days and I think it's an important thing to have.

I can give right to the npm package to anybody that needs them.

Anyway, good luck maintaining docson !

On Fri, Feb 2, 2018, 19:49 Laurent Bovet notifications@github.com wrote:

Yes, do it like you feel. You can merge the open PRs on a branch of yours and then merge this on master when ready to release (via a self-PR). This way, it is easy to have a look at all changes at once. I do not want to veto or slow you down, just have the possiblity to easily follow the upcoming history you are about to write :) Happy merging!

On Fri, Feb 2, 2018 at 5:47 PM Yanick Champoux notifications@github.com wrote:

Heh. That was easy. Thanks! :-)

@lbovet https://github.com/lbovet Do you have any protocol we should follow in mind (having you veto PRs that can be merged to master, etc), or should I merge things to master as I think it makes sense, and poke you went I think a release is ready?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lbovet/docson/issues/56#issuecomment-362615802, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAqPnHTa_TvqtuwidkfbjAtWdJ6zSRXRks5tQygqgaJpZM4RDpcx

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lbovet/docson/issues/56#issuecomment-362668457, or mute the thread https://github.com/notifications/unsubscribe-auth/ACPN_sePdno-JhSe1fE2CyNsYklV6Zt5ks5tQ1XxgaJpZM4RDpcx .

[rom1504]

Ah, it looks like I didn't make a pr. I meant https://github.com/rom1504/docson/commits/npm

I can open a PR if you're interested.

On Fri, Feb 2, 2018, 20:30 Romain Beaumont romain.rom1@gmail.com wrote:

If I could advise something, it might be interesting to have a look at my PR about putting docson on npm. Npm is the way front end is done these days and I think it's an important thing to have.

I can give right to the npm package to anybody that needs them.

Anyway, good luck maintaining docson !

On Fri, Feb 2, 2018, 19:49 Laurent Bovet notifications@github.com wrote:

Yes, do it like you feel. You can merge the open PRs on a branch of yours and then merge this on master when ready to release (via a self-PR). This way, it is easy to have a look at all changes at once. I do not want to veto or slow you down, just have the possiblity to easily follow the upcoming history you are about to write :) Happy merging!

On Fri, Feb 2, 2018 at 5:47 PM Yanick Champoux notifications@github.com wrote:

Heh. That was easy. Thanks! :-)

@lbovet https://github.com/lbovet Do you have any protocol we should follow in mind (having you veto PRs that can be merged to master, etc), or should I merge things to master as I think it makes sense, and poke you went I think a release is ready?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lbovet/docson/issues/56#issuecomment-362615802, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAqPnHTa_TvqtuwidkfbjAtWdJ6zSRXRks5tQygqgaJpZM4RDpcx

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lbovet/docson/issues/56#issuecomment-362668457, or mute the thread https://github.com/notifications/unsubscribe-auth/ACPN_sePdno-JhSe1fE2CyNsYklV6Zt5ks5tQ1XxgaJpZM4RDpcx .

[yanick]

@rom1504

I can open a PR if you're interested.

I'd love to see a PR. :-)

[yanick]

One new release has been made. I'll get cocky and close this ticket as 'resolved'. :-)