Sounds good. Using the self-service platform it indeed is fairly easy to
request the mailing list(s) ;)

Roy

Op zo 30 dec. 2018 om 18:01 schreef Christofer Dutz <
christofer.d...@c-ware.de>:

> I think creating them wouldn't be a huge overhead ...
>
> and then we could simply notify the dev-lists of the projects tagged with
> a given category about the new list.
> This way anyone could signup.
>
> Chris
>
> Am 30.12.18, 17:38 schrieb "Roy Lenferink" <rlenfer...@apache.org>:
>
>     Are we starting with iot@ or are we creating other lists as well, e.g.
>     streaming@ (Flink, Spark, Storm, Heron .....) and big-data@ (Hadoop,
> Metron
>     ....) and so on.
>     And were do we document the existence of these lists or do we leave it
> to
>     the projects if they want to point to the iot@a.o (as an example)
> mailing
>     list?
>
>     - Roy
>
>     Op zo 30 dec. 2018 om 14:56 schreef Christofer Dutz <
>     christofer.d...@c-ware.de>:
>
>     > So how would we create such a list?
>     >
>     > Chris
>     >
>     > Am 17.12.18, 09:44 schrieb "Christofer Dutz" <
> christofer.d...@c-ware.de>:
>     >
>     >     Well I'd be happy to help moderating this. What's "one more
> list" in
>     > the moderation inbox?
>     >
>     >     Do we have to vote on setting up the "i...@apache.org" list ...
> if yes
>     > ... do we do it here? Or could someone just create it.
>     >
>     >
>     >     Chris
>     >
>     >     PS: Do we have a web-tool for moderation? Right now all
> moderators get
>     > the same email and I can't see if someone else already accepted or
> rejected
>     > a message ... would be great if there was some "moderation inbox"
> with
>     > accept and reject buttons to quickly moderate all lists someone is
> listed
>     > as moderator for.
>     >
>     >
>     >     Am 16.12.18, 14:53 schrieb "Rich Bowen" <rbo...@rcbowen.com>:
>     >
>     >         +1 to the concept, and there's precedent with the geospatial
> list.
>     >
>     >         Bertrand mentions the tech@ list but I don't think anybody
> knows
>     > that it's
>     >         there or what it is for. Lists with topic names seem to have
> better
>     >         discoverability.
>     >
>     >         Note also that they attract more spam so ensure that you
> have some
>     > willing
>     >         moderators.
>     >
>     >         I think an iot@ list is a great way to attract new
> participants
>     > who aren't
>     >         already aware of the various projects and what they do.
>     >
>     >         On Thu, Dec 13, 2018, 03:34 Christofer Dutz <
>     > christofer.d...@c-ware.de
>     >         wrote:
>     >
>     >         > Hi all,
>     >         >
>     >         > at the moment I’m involved in 3 Apache project in the IoT
> area.
>     > A lot of
>     >         > the work I have been doing is to help make all of these
> work
>     > together.
>     >         > PLC4X – NiFi Integration
>     >         > PLC4X – Apache Kafka Connect
>     >         > PLC4X – Camel Integration
>     >         > PLC4X – Edgent Integration
>     >         > Edgent - … integration
>     >         >
>     >         > However sometimes I could for example need some help by
> NiFi
>     > Guys to check
>     >         > my NiFi integration, have Kafka Connect gurus provide
>     > suggestions on how to
>     >         > improve our connector, …
>     >         >
>     >         > There’s a lot happening here and signing up and keeping up
> to
>     > date for all
>     >         > the dev-lists of all the projects around here would leave
> no
>     > time to
>     >         > actually work on things.
>     >         >
>     >         > So my idea is: As we have a list of general categories for
> our
>     > projects,
>     >         > how about creating general “@apache.org” mailinglists for
> each
>     > of these
>     >         > categories for the purpose of coordinating such efforts.
>     >         >
>     >         > What do you think?
>     >         >
>     >         >
>     >         > Chris
>     >         >
>     >
>     >
>     >
>     >
>  ---------------------------------------------------------------------
>     >     To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>     >     For additional commands, e-mail: dev-h...@community.apache.org
>     >
>     >
>     >
>     >
>     > ---------------------------------------------------------------------
>     > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>     > For additional commands, e-mail: dev-h...@community.apache.org
>     >
>     >
>
>
>

Reply via email to