Update all composer.json for the `support` entry
Hywan opened this issue · 23 comments
The support
entry is set to:
"support": {
"email" : "support@lists.hoa-project.net",
"irc" : "irc://irc.freenode.org/hoaproject",
"source": "http://git.hoa-project.net/"
},
This is wrong for the email
part. We must fix it. Any proposal @hoaproject/hoackers?
See #37 (comment) for the diff and issue templates.
Progression
-
Acl
, -
Bench
, -
Cache
, -
Cli
, -
Compiler
, -
Consistency
, -
Console
, -
Core
, -
Database
, -
Devtools
, -
Dispatcher
, -
Dns
, -
Event
, -
Eventsource
, -
Exception
, -
Fastcgi
, -
File
, -
Graph
, -
Http
, -
Irc
, -
Iterator
, -
Json
, -
Locale
, -
Log
, -
Mail
, -
Math
, -
Memory
, -
Mime
, -
Model
, -
Notification
, -
Praspel
, -
Promise
, -
Protocol
, -
Prototype
, -
Realdom
, -
Regex
, -
Registry
, -
Router
, -
Ruler
, -
Serialize
, -
Session
, -
Socket
, -
Stream
, -
String
, -
Stringbuffer
, -
Test
, -
Translate
, -
Tree
, -
Ustring
, -
View
, -
Visitor
, -
Websocket
, -
Worker
, -
Xml
, -
Xmlrpc
, -
Xyl
, -
Zformat
, -
Zombie
, -
Discourse can create new topic from incoming email. We could create a new support@hoa-project.net redirection to discourse. What do you think about this solution ?
Yes this must be lead by discourse from now it should be the official communication way.
+1 for @osaris topic
I have added the progression section. Feel free to patch all the libraries!
It is already operational if we send email to support@hoa-project.net ?
I've setup category Support
it's seems work fine
The email we must used for create new Topic under Category Support is :
hoa_project+support@discoursemail.com
So now we have to update all composer.json
?
It should be preferable first to check if we can create an alias support@hoa-project.net
guess @Hywan can check-it on gandi
I am creating the alias.
I have written to support@hoa-project.net
and here the answer I got from hoa_project@discoursemail.com:
We're sorry, but your email message to ["support@hoa-project.net"](titled Testing auto-creation of Discourse topic from support@hoa) didn't work.
None of the destination email addresses are recognized. Please make sure that you are sending to the correct email address provided by staff.
you need to keep the +support
like this hoa_project+support@discoursemail.com
It's refer to the Category topic.
i've update config in discourse, it's works now!
We can go with this informations for composer.json
"support": {
"email" : "support@hoa-project.net",
"irc" : "irc://irc.freenode.org/hoaproject",
"forum" : "http://users.hoa-project.net",
"source" : "https://git.hoa-project.net"
}
@Pierozi Is it possible to have https://users.hoa
(which redirects to http://…
)? In case we have TLS one day, we won't need to rewrite all the composer.json
files.
It's not recommended because browser force cycle redirection...
OK, let's so like that.
So here is the patch to “apply” (not verbatim because lines change but the diff body should be identical)
"support": {
- "email" : "support@lists.hoa-project.net",
- "irc" : "irc://irc.freenode.org/hoaproject",
- "source": "http://git.hoa-project.net/"
+ "email" : "support@hoa-project.net",
+ "irc" : "irc://chat.freenode.net/hoaproject",
+ "forum" : "https://users.hoa-project.net/",
+ "docs" : "https://central.hoa-project.net/Documentation/Library/Acl",
+ "source": "https://central.hoa-project.net/Resource/Library/Acl"
},
What do we see?
- An updated
email
entry: No more mailing-lists, just a basic email, already configured to open a topic on Discourse, - An updated
irc
entry:freenode.org
redirects tofreenode.net
and the recommended domain ischat
, notirc
, - An updated
source
entry (pushed to the end of the list): Using the Central HTTP API to get the correct repository directly instead of the home of all repositories, - A new
forum
entry: Using ourusers.hoa-project.net
redirection to Discourse, - A new
docs
entry: Using the new Central HTTP API (see #40) to get a direct link to the appropriated hack book chapter.
All issues/PR must have the following template:
Address #37.
With the following labels: “enhancement”, “in progress” and “in progress”.
See hoaproject/Acl#21 for an example.
Thoughts @hoaproject/hoackers?
seems good for me
Any help is welcomed here :-).
Thank you all for your precious help! Now we have nice composer.json
files with useful links inside: IRC channel, mails to get help (with auto-post to our forum), forum, documentation and source!
👏 👏 👏 !