I recently started trying to contribute directly to the code of HtmlCleaner for fixing a bug I reported, and I discovered that it wasn't that easy to contribute and get feedbacks on sourceforge. At least, not as easy as it can be on Github (or Gitlab). And I'm wondering if moving the project couldn't help get more contributions and have bug fixed more quickly.
To give a bit of context, I'm one of the core committer of XWiki (https://www.xwiki.org) whose code in available on Github (https://github.com/xwiki). We use a lot HtmlCleaner in our project and so we found bug and request for features or improvments: we're very glad that the project exists and that we can use it. But personally I'd like to be able to contribute more easily and being an user of Github it feels like it could be a way to achieve that.
What do you think?
Thanks,
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it's a good time to talk about the future of the library in general. I'm aware that I don't have a lot of time available to maintain it, and these days I'm doing 99% Python development in my day job, so each time I have to review a patch my first task is to get a Java setup working again!
Certainly moving the project over to Github is something that's been on my mind for a while as there are clear advantages there.
I think in general I'd be happier if people who depend on HtmlCleaner were more able to move the project forward without relying on me as sole maintainer, particularly as I don't actually use it regularly myself these days.
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks for your answer.
So then what are the next steps and how can we plan such a move to Github? I see two options there:
1. you do the move, you're still owner and it's an official migration and we contribute through pull requests at least at first
2. you keep HtmlCleaner here and we create a fork on Github that we maintain there
personally I don't like option 2 and I'd really prefer to go towards option 1, but it depends on you.
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, is there any update to this migration?
I'm considering to adopt this library but I've some security-wise concerns.
Having this library on Github, it will make the fix of new CVE easier I think
Marco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I recently started trying to contribute directly to the code of HtmlCleaner for fixing a bug I reported, and I discovered that it wasn't that easy to contribute and get feedbacks on sourceforge. At least, not as easy as it can be on Github (or Gitlab). And I'm wondering if moving the project couldn't help get more contributions and have bug fixed more quickly.
To give a bit of context, I'm one of the core committer of XWiki (https://www.xwiki.org) whose code in available on Github (https://github.com/xwiki). We use a lot HtmlCleaner in our project and so we found bug and request for features or improvments: we're very glad that the project exists and that we can use it. But personally I'd like to be able to contribute more easily and being an user of Github it feels like it could be a way to achieve that.
What do you think?
Thanks,
Simon
Hi Simon,
I think it's a good time to talk about the future of the library in general. I'm aware that I don't have a lot of time available to maintain it, and these days I'm doing 99% Python development in my day job, so each time I have to review a patch my first task is to get a Java setup working again!
Certainly moving the project over to Github is something that's been on my mind for a while as there are clear advantages there.
I think in general I'd be happier if people who depend on HtmlCleaner were more able to move the project forward without relying on me as sole maintainer, particularly as I don't actually use it regularly myself these days.
Hi Scott,
thanks for your answer.
So then what are the next steps and how can we plan such a move to Github? I see two options there:
1. you do the move, you're still owner and it's an official migration and we contribute through pull requests at least at first
2. you keep HtmlCleaner here and we create a fork on Github that we maintain there
personally I don't like option 2 and I'd really prefer to go towards option 1, but it depends on you.
Simon
Hi, is there any update to this migration?
I'm considering to adopt this library but I've some security-wise concerns.
Having this library on Github, it will make the fix of new CVE easier I think
Marco
Hi Marco,
Its definitely going to happen, I just need to put the migration plan together.
Scott