flirmnave commented on pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#issuecomment-724465389
Thanks @cxorm @adoroszlai @smengcl @cku328 for review and comment.
I update it.
And add a section named **Older Archives**.
Can you please share your suggestions?
T
Thanks for taking this up Marton.
I played around with Github issues, projects & milestones. I like the
simplicity of the UI and the one stop place for all things related to
development. However, the objection around the project management related
limitations of Github seem valid. I am OK with try
>From what I can tell above, one of the concerns might not be mentioned (or
I might have missed it) is migration cost for people who didn't have
experience on Github issue. For people who only worked on JIRA in the
past, github issues might affect contributions from those people.
An assumption he
Thanks Marton for starting the discussion.
I like the proposal of integrating issue tracking with the repo. It would
greatly help with keeping the discussions in one place and avoid the extra step
of creating a Jira.
I personally have never worked with Github issues and as such I am not famili
Hi,
I wanted to start a new thread to get consensus on the latest approach for
the Ozone trash feature since it has been a while.
This is my understanding of the current plan from today's community call:
Phase 1: HDDS-2416
- This will reuse the existing deletedTable for simplicity to help pr
Thanks all for the discussion. I have similar concerns around function
completeness of Github issues. For example, are we going to miss JIRA's
flexible query with filtering and comprehensive role/permission management,
etc?
This may not be a fair comparison as JIRA is targeted as a project
managem
Thanks for starting this thread Marton.
I have worked with Github issues for other projects and find the
tracking rudimentary.
Basically absence of good queries, saving older queries, lack of
dashboards are my biggest objections to this.
I feel we can use some of the plugins with Github and
cku328 commented on a change in pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#discussion_r519944036
##
File path: content/community.md
##
@@ -0,0 +1,43 @@
+---
+title: Ozone Community
+---
+
+## Ozone Mailing Lists
+
+### Developers
+
+If you’d like to contr
adoroszlai commented on a change in pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#discussion_r519951691
##
File path: content/community.md
##
@@ -0,0 +1,43 @@
+---
+title: Ozone Community
+---
+
+## Ozone Mailing Lists
+
+### Developers
+
+If you’d like to c
cku328 commented on a change in pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#discussion_r519944036
##
File path: content/community.md
##
@@ -0,0 +1,43 @@
+---
+title: Ozone Community
+---
+
+## Ozone Mailing Lists
+
+### Developers
+
+If you’d like to contr
cxorm commented on pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#issuecomment-724111822
> Thanks @flirmnave for working on this. Looks good, but the email address
links need `mailto:` protocol. Otherwise they are treated as web links and
result in 404.
Thanks @ad
Marton, you should start a vote thread to get official consensus/objections.
> I feel that everybody is interested to try it out
Need more details here before proceeding.
Personally I am not in favor but if there is broad consensus from the community
I will not object.
Thanks,
Arpit
> On No
smengcl commented on a change in pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#discussion_r519903672
##
File path: content/community.md
##
@@ -0,0 +1,43 @@
+---
+title: Ozone Community
+---
+
+## Ozone Mailing Lists
+
+### Developers
+
+If you’d like to cont
A quick summary about this thread:
1. Github seems to provide better user experience, and easier
contribution possibilities
2. If (!) we can live with the current structure of Github / limitations.
Based on the discussion from the last sync, I feel that everybody is
interested to try
Thank you very much, it's extremely useful insight.
Marton
ps: I have some proposals to resolve this thread, will add to the thread
as a new mail.
On 11/1/20 8:17 PM, anu engineer wrote:
This is Anecdotal data -- However I thought it might be useful to share.
In my current project(Unfortu
flirmnave commented on pull request #1:
URL: https://github.com/apache/ozone-site/pull/1#issuecomment-723851498
Thanks @adoroszlai for review and comment.
I fix it.
This is an automated message from the Apache Git Service.
16 matches
Mail list logo
