ctubbsii commented on issue #340: URL: https://github.com/apache/accumulo-website/issues/340#issuecomment-1249834226
> I was proposing `we may want to structure our documentation to adopt the conventions suggested.` That could be using the file naming convention, updating or adopting policy statements.... If I recall, there was a checklist - how many do we already comply with, how many are we close to if we just ..., which ones may not be something that we do not agree with or cannot adopt? If someone went through that and presented it - that would be helpful. Even if we do not have an EOL as they define it, using those conventions to make it clear that we don't, in a common form may be useful I went through the checklist on their site, and we're already doing all the things that apply to us... which is why I was asking for a specific thing you think should be done. I don't see anything to do here that we're not already doing. > > I created it as an issue so that it would be visible to individuals that may want to contribute and maybe don't have a strong programming background. While it is likely that some discussions may need to occur on one of our mail list to get consensus on any policy changes, as an issue it has a wider audience. If this was only a discussion on our mailing list, outside individuals would certainly have a harder time finding it. As an issue it remains visible as a task that can be done by anyone that would like to pick this up and run with it. That's fine... but for tasks to be useful, they must be actionable for people to help out. I don't see anything actionable here. There's nothing to do as far as I can tell. > > If no one expresses interest, we will evaluate if it is useful, or just close it. I think it is something that should be looked at and maybe I'll find time to look at it closer, until then (and hopefully) someone else will pick it up. I've looked at it already... and evaluated it, and I don't think it's useful. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
