Hi, On Thu, Nov 30, 2017 at 11:22 AM, Piergiorgio Lucidi <piergior...@apache.org> wrote: > ...I'm wondering if CrafterCMS [1] can > help us for this because it is a Git-based CMS and it is also Open Source > :)...
I don't think tools is the problem here, if we have a team the tools will follow. https://community.apache.org/ is currently published using the Apache CMS which infra gradually wants to retire, but it's not too hard to convert it to Git-based markdown content if someone volunteers for that. I did that for Sling recently [1] and we have several other examples. The comdev website [2] is only about 60 pages. I don't think we have cycles to sustainably manage more complex tools and I don't think that's needed. As for a team I would treat this as we do with PMCs: only publish pages in a given language if we have at least 3 active comdev PMC members willing to manage those translations, and remove those pages if that condition isn't true anymore. We don't want stale content of translations on which we have no oversight due to lack of language skills. -Bertrand [1] https://issues.apache.org/jira/browse/SLING-6955 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
