Hi, Igor, Can you logon to minotaur.apache.org? people.apache.org is changed to scp only.
Eventually you will generate static website and sync to /www/knox.apache.org on minotaur (using svnpubsub). Usually you will need use some authoring tool to generate static html. For Pig, we use Apache Forrest. Here is the website source code for Pig: https://svn.apache.org/repos/asf/pig/site/author/ But there are other alternatives for sure. Thanks, Daniel From: Igor Katkov <katk...@yahoo-inc.com<mailto:katk...@yahoo-inc.com>> Reply-To: Igor Katkov <katk...@yahoo-inc.com<mailto:katk...@yahoo-inc.com>> Date: Monday, April 11, 2016 at 4:52 PM To: "dev@omid.incubator.apache.org<mailto:dev@omid.incubator.apache.org>" <dev@omid.incubator.apache.org<mailto:dev@omid.incubator.apache.org>>, daijy <da...@hortonworks.com<mailto:da...@hortonworks.com>> Subject: Re: Omid bootstrap Hi Daniel, Wrt website, I assume we are supposed to generate static htmls and upload them somewhere. Is that correct? Where do these go? Is this the right place ? people.apache.org: /www/omid.apache.org/content/ Are we supposed to have ssh access to people.apache.org using private/pub key? The latest does not work for us, we have "LDAP authorisation check failed" error. debug2: key: /Users/katkovi/.ssh/id_dsa (0x7fa913e003d0), debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/katkovi/.ssh/id_rsa debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 279 debug2: input_userauth_pk_ok: fp f0:48:4f:38:e3:30:73:ef:dc:9d:c8:be:4a:ba:c9:86 debug1: read PEM private key done: type RSA LDAP authorisation check failed On Friday, April 8, 2016 10:54 AM, 'Francisco Perez-Sorrosal' via Omid Dev <omid-...@googlegroups.com<mailto:omid-...@googlegroups.com>> wrote: Hi Flavio, Thanks for your offering. We'll try to do the transition as soon as possible. I guess it would be useful to create a JiRA story for the transition from Github to Apache infrastructure, creating the corresponding tasks. We can start with that. Regarding the logo, we have a design that is currently in the Github project page since we open-sourced the second version of Omid. I worked on that with a colleague, with the idea of representing a pipeline of transactional tasks and connections. Starting and ending with two circles representing the transactions (The first acting as O and the latter as the I and D in Omid) the M letter represented the connections. Some people don't like it because they say they can not read the word Omid. If people don't like it, we can try to make it more readable, for example emptying the O and the D to make them more clear. Regarding the Twitter account, I already had one created. I changed the name to the one you suggested and changed the email to the one for the private incubator list. Thanks. Best regards, Francisco On Friday, April 8, 2016 2:51 AM, Flavio Junqueira <f...@apache.org<mailto:f...@apache.org>> wrote: Thanks for doing all this, Daniel. As for the next steps, it'd be great to have the initial code dump and an initial web site created soon. Let me know if there is any way I can help. While thinking about the web site, I remembered that for ZK and BK we had someone at Yahoo! to do the logo for us. Do you guys have a logo already or someone to create a logo for the project? It might also be nice to secure the @apacheomid twitter handle. -Flavio > On 07 Apr 2016, at 23:13, Daniel Dai > <da...@hortonworks.com<mailto:da...@hortonworks.com>> wrote: > > Omid bootstrap is done. Here are the resources available now: > > * mailing list: > priv...@omid.incubator.apache.org<mailto:priv...@omid.incubator.apache.org>, > dev@omid.incubator.apache.org<mailto:dev@omid.incubator.apache.org>, > comm...@omid.incubator.apache.org<mailto:comm...@omid.incubator.apache.org> > are created. Please subscribe by writing an email to: > private-subscr...@omid.incubator.apache.org<mailto:private-subscr...@omid.incubator.apache.org>, > > dev-subscr...@omid.incubator.apache.org<mailto:dev-subscr...@omid.incubator.apache.org>, > > commits-subscr...@omid.incubator.apache.org.<mailto:commits-subscr...@omid.incubator.apache.org.> > We shall stop using > omid-...@googlegroups.com<mailto:omid-...@googlegroups.com> and use > priv...@omid.incubator.apache.org<mailto:priv...@omid.incubator.apache.org>, > dev@omid.incubator.apache.org<mailto:dev@omid.incubator.apache.org> for > discussion > * Git repo: https://git-wip-us.apache.org/repos/asf/incubator-omid.git, all > committers should have read/write permission now > * Jira: https://issues.apache.org/jira/browse/OMID, I added committers has > Jira accounts to committer group. I made Francisco admin for the Jira > project, so he can add new committers to the committer group going forward. > > Next step: > > * Initial code dump to git after IP Clearance > (http://incubator.apache.org/guides/mentor.html#initial-ip-clearance) > * Create website > (http://incubator.apache.org/guides/mentor.html#create-website) > > Going forward maintenance: > > * Update status page http://incubator.apache.org/projects/omid.html > according to > http://incubator.apache.org/guides/website.html#Edit+your+project+status+page > * Quarterly status report > (http://incubator.apache.org/guides/ppmc.html#Incubator+ASF+Board+Reports), > the first report due on June > > Enjoy! > > Let me know if you have any questions. > > Thanks, > Daniel -- You received this message because you are subscribed to the Google Groups "Omid Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to omid-dev+unsubscr...@googlegroups.com<mailto:omid-dev+unsubscr...@googlegroups.com>. To post to this group, send email to omid-...@googlegroups.com<mailto:omid-...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/omid-dev/448677102.266065.1460138014881.JavaMail.yahoo%40mail.yahoo.com<https://groups.google.com/d/msgid/omid-dev/448677102.266065.1460138014881.JavaMail.yahoo%40mail.yahoo.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout.
