[jira] [Commented] (COMDEV-307) GSoC - Allura - responsive web pages
[ https://issues.apache.org/jira/browse/COMDEV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799334#comment-16799334 ] Dave Brondsema commented on COMDEV-307: --- Hi [~dilshandilip] I'd recommend first installing Allura and getting it running so you can be familiar with it. Then you could try experimenting with a simple page template and see how it works. Join our dev mailing list at [https://lists.apache.org/list.html?d...@allura.apache.org] to ask any questions. It'd be good to do some initial small work with Allura (see the contributing section of the docs). > GSoC - Allura - responsive web pages > > > Key: COMDEV-307 > URL: https://issues.apache.org/jira/browse/COMDEV-307 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: css, gsoc2019, html, javascript, sass, ux > > Allura's web frontend should be responsive. Initial prototyping work has > begun using the Foundation framework: > [https://foundation.zurb.com/sites/docs/] More initial work needs to be done > to develop a reliable pattern, and then convert existing templates to use > Foundation HTML markup and CSS (SCSS, actually) to layout the pages in an > intuitive way for all screen sizes. Interactivity via JS may need to be > updated as well. Some more details are here > [https://lists.apache.org/thread.html/f441cef1d288410be5b6c6fc521d62d350ba92df5b4c0e84ea734d5d@%3Cdev.allura.apache.org%3E] > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-307) GSoC - Allura - responsive web pages
[ https://issues.apache.org/jira/browse/COMDEV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782498#comment-16782498 ] Dave Brondsema commented on COMDEV-307: --- [~nayanagamuhandiram] you should join the dev mailing list at [https://lists.apache.org/list.html?d...@allura.apache.org] and introduce yourself. That's the best place to ask questions about Allura. I would recommend first installing Allura and getting it running so you can be familiar with it. Then you could try experimenting with a simple page template and see how it works. > GSoC - Allura - responsive web pages > > > Key: COMDEV-307 > URL: https://issues.apache.org/jira/browse/COMDEV-307 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: css, gsoc2019, html, javascript, sass, ux > > Allura's web frontend should be responsive. Initial prototyping work has > begun using the Foundation framework: > [https://foundation.zurb.com/sites/docs/] More initial work needs to be done > to develop a reliable pattern, and then convert existing templates to use > Foundation HTML markup and CSS (SCSS, actually) to layout the pages in an > intuitive way for all screen sizes. Interactivity via JS may need to be > updated as well. Some more details are here > [https://lists.apache.org/thread.html/f441cef1d288410be5b6c6fc521d62d350ba92df5b4c0e84ea734d5d@%3Cdev.allura.apache.org%3E] > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-306) GSoC - Allura - Convert to python 3
[ https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782126#comment-16782126 ] Dave Brondsema commented on COMDEV-306: --- [~Abhism] you should join the dev mailing list at [https://lists.apache.org/list.html?d...@allura.apache.org] and introduce yourself. That's the best place to ask questions about Allura. I would recommend first installing Allura and getting it running so you can be familiar with it. Then you could try upgrading one dependency from requirements.txt at a time, and see if everything works and tests pass still. That'd be a good starting task to try. > GSoC - Allura - Convert to python 3 > --- > > Key: COMDEV-306 > URL: https://issues.apache.org/jira/browse/COMDEV-306 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2019, python > > Allura is a large mature codebase, and relies on many dependencies. The path > to python 3 will have many steps, but we need to start working on it. GSOC > work would include familiarizing with porting guides like > [https://docs.python.org/3/howto/pyporting.html] and > [https://portingguide.readthedocs.io/en/latest/] and > [http://python3porting.com/] and then working through steps like: > * upgrading dependencies, and updating code & tests to match > * removing or replacing dependencies where needed, and updating code > * running futurize or modernize, manual code changes where needed, cleanup, > etc > * testing > * documentation updates > * Docker updates > * more, probably :) > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-308) GSoC - Allura - importers / sync for Bitbucket and Gitlab
Dave Brondsema created COMDEV-308: - Summary: GSoC - Allura - importers / sync for Bitbucket and Gitlab Key: COMDEV-308 URL: https://issues.apache.org/jira/browse/COMDEV-308 Project: Community Development Issue Type: Improvement Components: GSoC/Mentoring ideas Reporter: Dave Brondsema Allura has a solid framework for doing imports, and has implemented this for services like GitHub, Google Code and Trac. It covers aspects from Git/Hg/SVN to tickets and wikis. It would be great to enhance this to support importing & converting data from Bitbucket and Gitlab. The level of integration & conversion may vary depending on the format and structure of the services. Beyond that, related improvements could be made in supporting ongoing synchronization of Git/Hg/SVN repositories (not just a one-time import). Or importers for JIRA, or improving importing of Allura's own formats. Everything in the ForgeImporters directory is our existing import system. The forgeimporters/base.py file has several base classes that provide common functionality for all importers to use. In the subdirectories "forge" "github" and "google" there are specific importers that can be good examples to reference. Importers can also be external packages, see these repos as more examples: [https://sourceforge.net/p/mediawikiimporter/git/ci/master/tree/] and [https://sourceforge.net/p/tracwikiimporter/git/ci/master/tree/] https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-307) GSoC - Allura - responsive web pages
Dave Brondsema created COMDEV-307: - Summary: GSoC - Allura - responsive web pages Key: COMDEV-307 URL: https://issues.apache.org/jira/browse/COMDEV-307 Project: Community Development Issue Type: Improvement Components: GSoC/Mentoring ideas Reporter: Dave Brondsema Allura's web frontend should be responsive. Initial prototyping work has begun using the Foundation framework: [https://foundation.zurb.com/sites/docs/] More initial work needs to be done to develop a reliable pattern, and then convert existing templates to use Foundation HTML markup and CSS (SCSS, actually) to layout the pages in an intuitive way for all screen sizes. Interactivity via JS may need to be updated as well. Some more details are here [https://lists.apache.org/thread.html/f441cef1d288410be5b6c6fc521d62d350ba92df5b4c0e84ea734d5d@%3Cdev.allura.apache.org%3E] https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-306) GSoC - Allura - Convert to python 3
[ https://issues.apache.org/jira/browse/COMDEV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Brondsema updated COMDEV-306: -- Component/s: GSoC/Mentoring ideas > GSoC - Allura - Convert to python 3 > --- > > Key: COMDEV-306 > URL: https://issues.apache.org/jira/browse/COMDEV-306 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2019, python > > Allura is a large mature codebase, and relies on many dependencies. The path > to python 3 will have many steps, but we need to start working on it. GSOC > work would include familiarizing with porting guides like > [https://docs.python.org/3/howto/pyporting.html] and > [https://portingguide.readthedocs.io/en/latest/] and > [http://python3porting.com/] and then working through steps like: > * upgrading dependencies, and updating code & tests to match > * removing or replacing dependencies where needed, and updating code > * running futurize or modernize, manual code changes where needed, cleanup, > etc > * testing > * documentation updates > * Docker updates > * more, probably :) > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-306) GSoC - Allura - Convert to python 3
Dave Brondsema created COMDEV-306: - Summary: GSoC - Allura - Convert to python 3 Key: COMDEV-306 URL: https://issues.apache.org/jira/browse/COMDEV-306 Project: Community Development Issue Type: Improvement Reporter: Dave Brondsema Allura is a large mature codebase, and relies on many dependencies. The path to python 3 will have many steps, but we need to start working on it. GSOC work would include familiarizing with porting guides like [https://docs.python.org/3/howto/pyporting.html] and [https://portingguide.readthedocs.io/en/latest/] and [http://python3porting.com/] and then working through steps like: * upgrading dependencies, and updating code & tests to match * removing or replacing dependencies where needed, and updating code * running futurize or modernize, manual code changes where needed, cleanup, etc * testing * documentation updates * Docker updates * more, probably :) https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-256) Allura - importers / sync for Bitbucket and Gitlab
[ https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399542#comment-16399542 ] Dave Brondsema commented on COMDEV-256: --- Hi Nirmal, I would recommend you write up a draft of your proposal ideas and share it either on the Allura dev mailing list for public feedback, or to me privately if you prefer: [d...@brondsema.net|mailto:d...@brondsema.net] Getting feedback on your proposal is allowed and helpful. Also read [https://community.apache.org/gsoc.html] which has some good instructions about what makes a good application. A draft proposal and any of your questions about it would be good to see. It'd also be good for you to continue to learn the code base, and get involved with the small Allura community. Joining the Allura dev mailing list and introducing yourself is a good first step. Getting Allura up and running and making a very small change is good practice too. [https://forge-allura.apache.org/docs/development/contributing.html] is a good starting point for that. Thanks and good luck! -Dave > Allura - importers / sync for Bitbucket and Gitlab > -- > > Key: COMDEV-256 > URL: https://issues.apache.org/jira/browse/COMDEV-256 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2018, mongodb, python > > Allura has a solid framework for doing imports, and has implemented this for > services like GitHub, Google Code and Trac. It covers aspects from > Git/Hg/SVN to tickets and wikis. > It would be great to enhance this to support importing & converting data from > Bitbucket and Gitlab. The level of integration & conversion may vary > depending on the format and structure of the services. > Beyond that, related improvements could be made in supporting ongoing > synchronization of Git/Hg/SVN repositories (not just a one-time import). Or > importers for JIRA, or improving importing of Allura's own formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-256) Allura - importers / sync for Bitbucket and Gitlab
[ https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379465#comment-16379465 ] Dave Brondsema commented on COMDEV-256: --- [https://forge-allura.apache.org/docs/development/extending.html] doesn't mention importers at all, but it should because importers are another way to extend Allura. So I was thinking as you learn about importers, you could write a little bit of explanation that could be added to that documentation page. Writing about what you learn can be a helpful way to learn if you want. If you do want to try that, feel free to send something on the mailing list and we can help too. > Allura - importers / sync for Bitbucket and Gitlab > -- > > Key: COMDEV-256 > URL: https://issues.apache.org/jira/browse/COMDEV-256 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2018, mongodb, python > > Allura has a solid framework for doing imports, and has implemented this for > services like GitHub, Google Code and Trac. It covers aspects from > Git/Hg/SVN to tickets and wikis. > It would be great to enhance this to support importing & converting data from > Bitbucket and Gitlab. The level of integration & conversion may vary > depending on the format and structure of the services. > Beyond that, related improvements could be made in supporting ongoing > synchronization of Git/Hg/SVN repositories (not just a one-time import). Or > importers for JIRA, or improving importing of Allura's own formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-255) Allura - merge request improvements
[ https://issues.apache.org/jira/browse/COMDEV-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379455#comment-16379455 ] Dave Brondsema commented on COMDEV-255: --- Hi, We have documentation about Allura at [https://forge-allura.apache.org/docs/index.html] See the Contributing section if you want to start learning how the codebase works. Our mailing list is a good place for any further questions or ideas: https://lists.apache.org/list.html?d...@allura.apache.org > Allura - merge request improvements > --- > > Key: COMDEV-255 > URL: https://issues.apache.org/jira/browse/COMDEV-255 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: git, gsoc2018, hg, mongodb, python > > Allura supports merge requests for its Git and Hg functionality, but it could > be made better. This would involve python, git, and hg. Also HTML/CSS/JS. > Here are some ideas for improvement, of varying difficulty: > * automatically update when new commits are pushed > [https://forge-allura.apache.org/p/allura/tickets/5993/] > * preview commits [https://forge-allura.apache.org/p/allura/tickets/6581/] > * better display after merging > [https://forge-allura.apache.org/p/allura/tickets/7879/] > * branch comparison [https://forge-allura.apache.org/p/allura/tickets/5840/] > and/or [https://forge-allura.apache.org/p/allura/tickets/7241/] > * commenting on individual lines/chunks of diffs > [https://forge-allura.apache.org/p/allura/tickets/7241/] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-254) Allura - personal dashboard
[ https://issues.apache.org/jira/browse/COMDEV-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379453#comment-16379453 ] Dave Brondsema commented on COMDEV-254: --- Hi, We have documentation about Allura at [https://forge-allura.apache.org/docs/index.html] See the Contributing section if you want to start learning how the codebase works. Our mailing list is a good place for any further questions or ideas: https://lists.apache.org/list.html?d...@allura.apache.org > Allura - personal dashboard > --- > > Key: COMDEV-254 > URL: https://issues.apache.org/jira/browse/COMDEV-254 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2018, mongodb, python > > A nice improvement to Allura project/code hosting would be a personal > dashboard when you are logged in. It would provide quick access to the > projects you are a part of, tickets you have created, tickets assigned to > you, your pull requests, activity stream of people you follow, etc. > Since there are many possible components to this, a pluggable structure like > the user profile page would be good. Some parts of a public profile (like > projects list) could be re-used on the personal dashboard too. > [https://forge-allura.apache.org/p/allura/tickets/7171/] is a related Allura > ticket about seeing your own ticket votes. Many new tickets for the whole > dashboard idea would have to be created to divide it into manageable tasks. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-256) Allura - importers / sync for Bitbucket and Gitlab
[ https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372992#comment-16372992 ] Dave Brondsema commented on COMDEV-256: --- You can subscribe by sending a mail to dev-subscr...@allura.apache.org > Allura - importers / sync for Bitbucket and Gitlab > -- > > Key: COMDEV-256 > URL: https://issues.apache.org/jira/browse/COMDEV-256 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2018, mongodb, python > > Allura has a solid framework for doing imports, and has implemented this for > services like GitHub, Google Code and Trac. It covers aspects from > Git/Hg/SVN to tickets and wikis. > It would be great to enhance this to support importing & converting data from > Bitbucket and Gitlab. The level of integration & conversion may vary > depending on the format and structure of the services. > Beyond that, related improvements could be made in supporting ongoing > synchronization of Git/Hg/SVN repositories (not just a one-time import). Or > importers for JIRA, or improving importing of Allura's own formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-256) Allura - importers / sync for Bitbucket and Gitlab
[ https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372205#comment-16372205 ] Dave Brondsema commented on COMDEV-256: --- Hi Nirmal, On [https://forge-allura.apache.org/docs/development/extending.html] we have some documentation about extension points, but I see now that it really doesn't explain the importer extension system yet. So maybe a nice first step as you learn would be to help us improve that documentation. So you will have to look at the source code. Everything in the ForgeImporters directory is our existing import system. The forgeimporters/base.py file has several base classes that provide common functionality for all importers to use (you don't need to understand everything in that file). And then you can see in the subdirectories "forge" "github" and "google" there are specific importers that can be good examples to reference. Importers can also be external packages, see these repos as more examples: [https://sourceforge.net/p/mediawikiimporter/git/ci/master/tree/] and https://sourceforge.net/p/tracwikiimporter/git/ci/master/tree/ I would recommend you join our dev mailing list and have any followup questions & ideas. https://mail-archives.apache.org/mod_mbox/allura-dev/ Thanks! > Allura - importers / sync for Bitbucket and Gitlab > -- > > Key: COMDEV-256 > URL: https://issues.apache.org/jira/browse/COMDEV-256 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: gsoc2018, mongodb, python > > Allura has a solid framework for doing imports, and has implemented this for > services like GitHub, Google Code and Trac. It covers aspects from > Git/Hg/SVN to tickets and wikis. > It would be great to enhance this to support importing & converting data from > Bitbucket and Gitlab. The level of integration & conversion may vary > depending on the format and structure of the services. > Beyond that, related improvements could be made in supporting ongoing > synchronization of Git/Hg/SVN repositories (not just a one-time import). Or > importers for JIRA, or improving importing of Allura's own formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-256) Allura - importers / sync for Bitbucket and Gitlab
Dave Brondsema created COMDEV-256: - Summary: Allura - importers / sync for Bitbucket and Gitlab Key: COMDEV-256 URL: https://issues.apache.org/jira/browse/COMDEV-256 Project: Community Development Issue Type: New Feature Components: GSoC/Mentoring ideas Reporter: Dave Brondsema Allura has a solid framework for doing imports, and has implemented this for services like GitHub, Google Code and Trac. It covers aspects from Git/Hg/SVN to tickets and wikis. It would be great to enhance this to support importing & converting data from Bitbucket and Gitlab. The level of integration & conversion may vary depending on the format and structure of the services. Beyond that, related improvements could be made in supporting ongoing synchronization of Git/Hg/SVN repositories (not just a one-time import). Or importers for JIRA, or improving importing of Allura's own formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-255) Allura - merge request improvements
Dave Brondsema created COMDEV-255: - Summary: Allura - merge request improvements Key: COMDEV-255 URL: https://issues.apache.org/jira/browse/COMDEV-255 Project: Community Development Issue Type: New Feature Components: GSoC/Mentoring ideas Reporter: Dave Brondsema Allura supports merge requests for its Git and Hg functionality, but it could be made better. This would involve python, git, and hg. Also HTML/CSS/JS. Here are some ideas for improvement, of varying difficulty: * automatically update when new commits are pushed [https://forge-allura.apache.org/p/allura/tickets/5993/] * preview commits [https://forge-allura.apache.org/p/allura/tickets/6581/] * better display after merging [https://forge-allura.apache.org/p/allura/tickets/7879/] * branch comparison [https://forge-allura.apache.org/p/allura/tickets/5840/] and/or [https://forge-allura.apache.org/p/allura/tickets/7241/] * commenting on individual lines/chunks of diffs [https://forge-allura.apache.org/p/allura/tickets/7241/] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-254) Allura - personal dashboard
Dave Brondsema created COMDEV-254: - Summary: Allura - personal dashboard Key: COMDEV-254 URL: https://issues.apache.org/jira/browse/COMDEV-254 Project: Community Development Issue Type: New Feature Components: GSoC/Mentoring ideas Reporter: Dave Brondsema A nice improvement to Allura project/code hosting would be a personal dashboard when you are logged in. It would provide quick access to the projects you are a part of, tickets you have created, tickets assigned to you, your pull requests, activity stream of people you follow, etc. Since there are many possible components to this, a pluggable structure like the user profile page would be good. Some parts of a public profile (like projects list) could be re-used on the personal dashboard too. [https://forge-allura.apache.org/p/allura/tickets/7171/] is a related Allura ticket about seeing your own ticket votes. Many new tickets for the whole dashboard idea would have to be created to divide it into manageable tasks. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
