Re: Podling S2graph Report Reminder - June 2020
On Wed, Jun 3, 2020 at 11:22 AM Woonsan Ko wrote: > > Hi, > > I've corrected the three obvious mistakes: > > ### Date of last release: 2017-08-26 (was 2019-02-05 for the next question) > ### When were the last committers or PPMC members elected? 2019-02-05 > (copied from the last February report as I didn't see any new > elections afterward.) > ### Have your mentors been helpful and responsive? (was placed in the > previous question) > Our mentor is very helpful and responsive. > > I don't know if our Podling has managed a brand / trademarks, so the > following question is with no answer: > ### Is the PPMC managing the podling's brand / trademarks? > > Daewon/Do Yung, could you give information about any brand/trandmarks > regarding S2Graph? More specifically, does your employer or any of you own the brand/trandmarks (S2Graph or somethings related) in Korea or US or other countries now? Thanks in advance, Woonsan > > Thanks, > > Woonsan > > On Tue, Jun 2, 2020 at 7:55 PM Justin Mclean wrote: > > > > Hi, > > > > Currently your report is incomplete and missing answer to these two > > questions: > > Have your mentors been helpful and responsive? > > Is the PPMC managing the podling's brand / trademarks? > > > > The report is due today and it would be good if you could answer these. > > > > Thanks, > > Justin
Re: Podling S2graph Report Reminder - June 2020
Hi, I've corrected the three obvious mistakes: ### Date of last release: 2017-08-26 (was 2019-02-05 for the next question) ### When were the last committers or PPMC members elected? 2019-02-05 (copied from the last February report as I didn't see any new elections afterward.) ### Have your mentors been helpful and responsive? (was placed in the previous question) Our mentor is very helpful and responsive. I don't know if our Podling has managed a brand / trademarks, so the following question is with no answer: ### Is the PPMC managing the podling's brand / trademarks? Daewon/Do Yung, could you give information about any brand/trandmarks regarding S2Graph? Thanks, Woonsan On Tue, Jun 2, 2020 at 7:55 PM Justin Mclean wrote: > > Hi, > > Currently your report is incomplete and missing answer to these two questions: > Have your mentors been helpful and responsive? > Is the PPMC managing the podling's brand / trademarks? > > The report is due today and it would be good if you could answer these. > > Thanks, > Justin
Writing in non-English is fine as long as explained or summarized in English
Just to remind everyone in dev mailing list here, it is totally fine to write your questions and messages not in English as long as the discussion is at least (sooner or later) explained or summarized in English to other developers. :-) In Korean, Chinese, Vietnamese, Japanese, etc, it is more than welcome! I believe most developers are willing to translate or help understand messages if necessary. Woonsan [In Korean] 확인 차원에서 말씀드리자면, 이 개발자 메일링 리스트에서, 적어도 조만간에 토론 내용이 다른 개발자들을 위해 영어로 설명되거나 요점 정리되어 제공되기만 한다면, 굳이 영어로 질문/답변을 올리지 않으셔도 됩니다. ^^ 한국어, 중국어, 베트남어, 일본어 등으로 올리셔도 무방하고, 적극 환영합니다. 필요한 경우, 거의 대부분의 개발자 분들은 메시지를 번역해 보거나 이해를 돕고자 할 것입니다.
Re: Podling S2graph Report Reminder - June 2020
Thank you very much, Daewon, for drafting the report and asking for reviews this time! It looks good to me! PPMC members and devs, please have a look and feel free to ask or discuss if there's any question. Cheers, Woonsan On Mon, Jun 1, 2020 at 9:36 AM blueiur wrote: > > Reported s2graph June 2020. > More activities are planned in the future. > > Thank you. > > https://cwiki.apache.org/confluence/display/INCUBATOR/June2020#s2graph > ``` > ## S2Graph > > S2Graph is a distributed and scalable OLTP graph database built on Apache > HBase to support fast traversal of extremely large graphs. > > S2Graph has been incubating since 2015-11-29. > > ### Three most important unfinished issues to address before graduating: > > 1. Make the third release > 2. Attract more users and contributors > 3. Build the developer community in both size and diversity > 4. Supporting the mordern ecosystem > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > None > > > ### How has the community developed since the last report? > > Not much activities > > ### How has the project developed since the last report? > > 1. One new contributor joined in community by submitting the PR(S2GRAPH-255) > 2. Create issue to support Scala ecosystem (S2GRAPH-258) > 3. Several bug fixes PR > - S2GRAPH-257: SafeUpdateCache#withCache method incorrect behavior > - S2GRAPH-259: column_metas miss default_value > - S2GRAPH-253: adding more api docs; rename deleteLabel to > deleteLabelReally > - S2GRAPH-256: Spelling mistakes > - S2GRAPH-255: Enable incremental processing of s2jobs > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [X] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > 2019-02-05 > > ### When were the last committers or PPMC members elected? > > Our mentor is very helpful and responsive. > (Thank you Woonsan Ko) > > ### Have your mentors been helpful and responsive? > Are things falling through the cracks? If so, please list any > open issues that need to be addressed. > > ### Is the PPMC managing the podling's brand / trademarks? > Are 3rd parties respecting and correctly using the podlings > name and brand? If not what actions has the PPMC taken to > correct this? Has the VP, Brand approved the project name? > > ### Signed-off-by: > > - [ ] (s2graph) Sergio Fernández > Comments: > - [ ] (s2graph) Woonsan Ko > Comments: > > ### IPMC/Shepherd notes: > ``` > > 2020년 6월 1일 (월) 오전 5:31, Woonsan Ko 님이 작성: > > > The wiki site is back! ^^ > > > > On Sun, May 31, 2020 at 10:43 AM Woonsan Ko wrote: > > > > > > The wiki site seems unavailable (503) at the moment. > > > Hope it come back soon. > > > > > > Woonsan > > > > > > On Wed, May 27, 2020 at 6:30 PM wrote: > > > > > > > > Dear podling, > > > > > > > > This email was sent by an automated system on behalf of the Apache > > > > Incubator PMC. It is an initial reminder to give you plenty of time to > > > > prepare your quarterly board report. > > > > > > > > The board meeting is scheduled for Wed, 17 June 2020. > > > > The report for your podling will form a part of the Incubator PMC > > > > report. The Incubator PMC requires your report to be submitted 2 weeks > > > > before the board meeting, to allow sufficient time for review and > > > > submission (Wed, June 03). > > > > > > > > Please submit your report with sufficient time to allow the Incubator > > > > PMC, and subsequently board members to review and digest. Again, the > > > > very latest you should submit your report is 2 weeks prior to the board > > > > meeting. > > > > > > > > Candidate names should not be made public before people are actually > > > > elected, so please do not include the names of potential committers or > > > > PPMC members in your report. > > > > > > > > Thanks, > > > > > > > > The Apache Incubator PMC > > > > > > > > Submitting your Report > > > > > > > > -- > > > > > > > > Your report should contain the following: > > > > > > > > * Your project name > > > > * A brief description of your project, which assumes no knowledge of &g
Re: Podling S2graph Report Reminder - June 2020
The wiki site is back! ^^ On Sun, May 31, 2020 at 10:43 AM Woonsan Ko wrote: > > The wiki site seems unavailable (503) at the moment. > Hope it come back soon. > > Woonsan > > On Wed, May 27, 2020 at 6:30 PM wrote: > > > > Dear podling, > > > > This email was sent by an automated system on behalf of the Apache > > Incubator PMC. It is an initial reminder to give you plenty of time to > > prepare your quarterly board report. > > > > The board meeting is scheduled for Wed, 17 June 2020. > > The report for your podling will form a part of the Incubator PMC > > report. The Incubator PMC requires your report to be submitted 2 weeks > > before the board meeting, to allow sufficient time for review and > > submission (Wed, June 03). > > > > Please submit your report with sufficient time to allow the Incubator > > PMC, and subsequently board members to review and digest. Again, the > > very latest you should submit your report is 2 weeks prior to the board > > meeting. > > > > Candidate names should not be made public before people are actually > > elected, so please do not include the names of potential committers or > > PPMC members in your report. > > > > Thanks, > > > > The Apache Incubator PMC > > > > Submitting your Report > > > > -- > > > > Your report should contain the following: > > > > * Your project name > > * A brief description of your project, which assumes no knowledge of > > the project or necessarily of its field > > * A list of the three most important issues to address in the move > > towards graduation. > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > > aware of > > * How has the community developed since the last report > > * How has the project developed since the last report. > > * How does the podling rate their own maturity. > > > > This should be appended to the Incubator Wiki page at: > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/June2020 > > > > Note: This is manually populated. You may need to wait a little before > > this page is created from a template. > > > > Note: The format of the report has changed to use markdown. > > > > Mentors > > --- > > > > Mentors should review reports for their project(s) and sign them off on > > the Incubator wiki page. Signing off reports shows that you are > > following the project - projects that are not signed may raise alarms > > for the Incubator PMC. > > > > Incubator PMC
Re: Podling S2graph Report Reminder - June 2020
The wiki site seems unavailable (503) at the moment. Hope it come back soon. Woonsan On Wed, May 27, 2020 at 6:30 PM wrote: > > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 17 June 2020. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, June 03). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://cwiki.apache.org/confluence/display/INCUBATOR/June2020 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Note: The format of the report has changed to use markdown. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC
Fwd: Podling S2graph Report Reminder - May 2020
Could someone in PPMC prepare the report for review before too late? Thanks in advance, Woonsan -- Forwarded message - From: Date: Tue, Apr 28, 2020 at 9:32 PM Subject: Podling S2graph Report Reminder - May 2020 To: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 May 2020. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, May 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/May2020 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Podling S2graph Report Reminder - November 2019
Oh and in the report I took the liberty to rephrase "... to discuss the future of the project" with "... to discuss how to grow the community", in order to reduce the weight. ;-) Feel free to edit if there's anything better. Woonsan On Wed, Nov 6, 2019 at 9:23 AM Woonsan Ko wrote: > > Hi Justin / Do Yung, > > Perhaps I can give some detail about the first question as I initially > asked them to meet in person during my visit in Seoul. As a mentor, it > was a bit hard to understand how active committers or users are doing > and feeling about things only through E-mail. So, I just wanted to > break the ice to chat anything. ;-) > Anyway, there's no specific decisions made, instead we just talked > these and those over the lunch for a short time, just giving kind of > brainstorming ideas on how to help grow our community. Also agreed to > continue discussion with new ideas in the mailinglist. > I've added may mentor's comment in the report like the following with > changing the message link from markmaill to ASF official mail archive > link (https://lists.apache.org/...): > > "In my visit in Seoul, I met the three active committers - Daewon, Do > Yung and Hwansung - over lunch, chatting informally face-to-face for > the first time about how to grow our community. There has not been > much project / community activity for last 1 year, but they were > passionate to stay in the community and started reorganizing their > work/time, trying to improve developer's experience and accessibility, > considering to support Java Client or even Spring Boot for new people, > by which they believe they can help grow the community. There's no > specific decision made yet but we agreed to continue discussion in the > mailinglist. It was great for me as a mentor too to understand each > other. See [1] for detail." > > As it was rather informal chat than any decisions yet, my summary will > probably suffice. > > And, I guess Do Yung meant "No JIRA tickets" resolved during the > period by "No issues". > Perhaps could it be rephrased to something like "No new features or > fixes made since last report"? > > Kind regards, > > Woonsan > > On Tue, Nov 5, 2019 at 8:33 PM Justin Mclean wrote: > > > > Hi, > > > > Thanks for submitting the report. It would be good to see more detail in > > the report. > > > > You mention a discussion about the future of they project, what if anything > > was decided/discussed? Rather than linking to an an email it would be good > > to include a summary of this in your report. > > > > Under how has the project developed you say "No issues has been resolved." > > what exactly do you mean by this? > > > > Thanks, > > Justin
Re: Podling S2graph Report Reminder - November 2019
Hi Justin / Do Yung, Perhaps I can give some detail about the first question as I initially asked them to meet in person during my visit in Seoul. As a mentor, it was a bit hard to understand how active committers or users are doing and feeling about things only through E-mail. So, I just wanted to break the ice to chat anything. ;-) Anyway, there's no specific decisions made, instead we just talked these and those over the lunch for a short time, just giving kind of brainstorming ideas on how to help grow our community. Also agreed to continue discussion with new ideas in the mailinglist. I've added may mentor's comment in the report like the following with changing the message link from markmaill to ASF official mail archive link (https://lists.apache.org/...): "In my visit in Seoul, I met the three active committers - Daewon, Do Yung and Hwansung - over lunch, chatting informally face-to-face for the first time about how to grow our community. There has not been much project / community activity for last 1 year, but they were passionate to stay in the community and started reorganizing their work/time, trying to improve developer's experience and accessibility, considering to support Java Client or even Spring Boot for new people, by which they believe they can help grow the community. There's no specific decision made yet but we agreed to continue discussion in the mailinglist. It was great for me as a mentor too to understand each other. See [1] for detail." As it was rather informal chat than any decisions yet, my summary will probably suffice. And, I guess Do Yung meant "No JIRA tickets" resolved during the period by "No issues". Perhaps could it be rephrased to something like "No new features or fixes made since last report"? Kind regards, Woonsan On Tue, Nov 5, 2019 at 8:33 PM Justin Mclean wrote: > > Hi, > > Thanks for submitting the report. It would be good to see more detail in the > report. > > You mention a discussion about the future of they project, what if anything > was decided/discussed? Rather than linking to an an email it would be good to > include a summary of this in your report. > > Under how has the project developed you say "No issues has been resolved." > what exactly do you mean by this? > > Thanks, > Justin
Re: Podling S2graph Report Reminder - November 2019
Thank you very much, Do Yung! Everything looks good to me. I'll sign off as soon as the wiki page is updated. Cheers, Woonsan On Mon, Nov 4, 2019 at 7:10 AM DO YUNG YOON wrote: > > Hi all. > Here is the draft for the report for November. > > S2Graph > > S2Graph is a distributed and scalable OLTP graph database built on Apache > HBase to support fast traversal of extremely large graphs. > > S2Graph has been incubating since 2015-11-29. > > Three most important issues to address in the move towards graduation: > > 1. Make the third release. > 2. Attract more users and contributors. > 3. Build the developer community in both size and diversity. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > None > > How has the community developed since the last report? > > * Not much activities. > * There was a meetup with active committers and a mentor to discuss the > future of the project. > - The link what we have discussed: > https://markmail.org/message/igdjlveeptsnskoh > > How has the project developed since the last report? > > * No issues has been resolved. > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] Initial setup > [ ] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > 2017-08-26 > > When were the last committers or PPMC members elected? > > Have your mentors been helpful and responsive or are things falling > through the cracks? In the latter case, please list any open issues > that need to be addressed. > > * Our mentor is very helpful and responsive. > > Signed-off-by: > > > > On Mon, Nov 4, 2019 at 5:55 AM Justin Mclean wrote: > > > Hi, > > > > Just a friendly reminder that this is due in a couple of days and I don't > > see any progress on it. It's best to work on the report in the open before > > it is due. > > > > Thanks, > > Justin > >
Re: Sharing offline discourse with active committers (Was: Meet and chat in Seoul area?)
And thank you so much, Do Yung, for inviting us to the delicious lunch! Also thanks to Daewon and Hwansung for coming far from the south and north in the metropolitan area during the day. Cheers, Woonsan On Wed, Oct 23, 2019 at 12:05 PM Woonsan Ko wrote: > > Hi folks in S2Graph community, > > I had a chance to visit Seoul for two months, even better I met and > chatted with some active committers - Daewon Jeong, Do Yung Yoon and > Hwansung Yu - over lunch in a Chinese restaurant in Seoul yesterday. > We discussed informally how we can help grow our community as well as > personal interests. So, even if it was a very short talk for about 1.5 > hr, I'd like to share a summary on what we discussed _informally_ > regarding community development issues with other developers and users > in this community. I believe this is compliant with the "Open > Communications" policy [1] in the Apache Way. ;-) > > 1. There has not been much project / community activity for last 1+ year. > I also had a concern about the progress. However, after having > talks face-to-face with the active committers, I was able to > understand what they had to face in their $dayjobs, working very hard > to successfully maintain a lot of S2Graph services in real sites > handling huge amount of traffics. They have tried to improve > documentation and API accessibility for new comers, just to give a few > examples, but it has been a struggle... Things seem to start changing. > They started reorganizing their work/time, and trying to find ways to > help new developers get involved more easily by improving the > developer experiences. Even if it looks slow-moving at this moment, > I'm personally confident with their passion as a mentor. > > 2. Various ideas on how to improve developer's experience were spoken. > For example, I personally mentioned that I tried to contribute > Swagger API documentation before but due to programming language > barrier - Scala which I had to start learning - it was very hard for > me to complete, adding "if it was Java, I could have been more > productive...". ;-) Daewon mentioned that they planned to provide a > Java client in the past and it is still something in their radar. > Also, I shared that Apache Jackrabbit has an option to run the JCR > server instance in-process residing in a web application, with an > alternative option to deploy the server instance in a separate process > to communicate with remotely. We may consider in the future that the > in-process option could be good to help developer's experience, too. > Like how developers feel confident and convenient nowadays with > spring-boot. > > 3. And we chatted on open source communities/cultures and business > models in general. > I don't think I can describe these properly as each topic was too > brief, scattered at random and it might sound a bit vague without > regional context information. Probably it's just worth mentioning that > we got better understandings on each by sharing same concerns and > information in these topics. > > All right. That's all I can recall. ;-) > Please feel free to add your thoughts in this thread if you have any > suggestions or insights. > I personally think this project has a unique value as the open source > graph database server in ASF. As the project artifacts have been used > successfully in big site's services, if we improve developer's > experiences and accessibility and so help grow the community, I > believe this will be a successful project and community in the end. I > have no doubt with the passions. > > Hope to have more formal/informal meetups - just over pizza for > example - in the future, too. Let's think about it, inviting more > people... Perhaps public/social-service offices may help as well. ;-) > > Kind regards, > > Woonsan > > [1] https://www.apache.org/theapacheway/ > > -- Forwarded message - > From: Woonsan Ko > Date: Wed, Aug 28, 2019 at 9:42 AM > Subject: Re: Meet and chat in Seoul area? > To: > > > Hi Hwansung, > > After Chuseok sounds good! :-) > > Regards, > > Woonsan > > > On Tue, Aug 27, 2019 at 8:16 PM Hwansung Yu wrote: > > > > Hi, > > > > I'm so happy to hear from you. > > How about late September after thanksgiving? > > > > Best regards, > > > > Hwansung > > > > > > 2019년 8월 27일 (화) 오후 9:05, Woonsan Ko 님이 작성: > > > > > Hi, > > > > > > I'm going to stay in South Korea in Sept. and Oct. If anyone is > > > willing to meet and chat (perhaps over beer), let me know. I'd be very > > > happy. ;-) > > > > > > Kind regards, > > > > > > Woonsan > > >
Sharing offline discourse with active committers (Was: Meet and chat in Seoul area?)
Hi folks in S2Graph community, I had a chance to visit Seoul for two months, even better I met and chatted with some active committers - Daewon Jeong, Do Yung Yoon and Hwansung Yu - over lunch in a Chinese restaurant in Seoul yesterday. We discussed informally how we can help grow our community as well as personal interests. So, even if it was a very short talk for about 1.5 hr, I'd like to share a summary on what we discussed _informally_ regarding community development issues with other developers and users in this community. I believe this is compliant with the "Open Communications" policy [1] in the Apache Way. ;-) 1. There has not been much project / community activity for last 1+ year. I also had a concern about the progress. However, after having talks face-to-face with the active committers, I was able to understand what they had to face in their $dayjobs, working very hard to successfully maintain a lot of S2Graph services in real sites handling huge amount of traffics. They have tried to improve documentation and API accessibility for new comers, just to give a few examples, but it has been a struggle... Things seem to start changing. They started reorganizing their work/time, and trying to find ways to help new developers get involved more easily by improving the developer experiences. Even if it looks slow-moving at this moment, I'm personally confident with their passion as a mentor. 2. Various ideas on how to improve developer's experience were spoken. For example, I personally mentioned that I tried to contribute Swagger API documentation before but due to programming language barrier - Scala which I had to start learning - it was very hard for me to complete, adding "if it was Java, I could have been more productive...". ;-) Daewon mentioned that they planned to provide a Java client in the past and it is still something in their radar. Also, I shared that Apache Jackrabbit has an option to run the JCR server instance in-process residing in a web application, with an alternative option to deploy the server instance in a separate process to communicate with remotely. We may consider in the future that the in-process option could be good to help developer's experience, too. Like how developers feel confident and convenient nowadays with spring-boot. 3. And we chatted on open source communities/cultures and business models in general. I don't think I can describe these properly as each topic was too brief, scattered at random and it might sound a bit vague without regional context information. Probably it's just worth mentioning that we got better understandings on each by sharing same concerns and information in these topics. All right. That's all I can recall. ;-) Please feel free to add your thoughts in this thread if you have any suggestions or insights. I personally think this project has a unique value as the open source graph database server in ASF. As the project artifacts have been used successfully in big site's services, if we improve developer's experiences and accessibility and so help grow the community, I believe this will be a successful project and community in the end. I have no doubt with the passions. Hope to have more formal/informal meetups - just over pizza for example - in the future, too. Let's think about it, inviting more people... Perhaps public/social-service offices may help as well. ;-) Kind regards, Woonsan [1] https://www.apache.org/theapacheway/ -- Forwarded message --------- From: Woonsan Ko Date: Wed, Aug 28, 2019 at 9:42 AM Subject: Re: Meet and chat in Seoul area? To: Hi Hwansung, After Chuseok sounds good! :-) Regards, Woonsan On Tue, Aug 27, 2019 at 8:16 PM Hwansung Yu wrote: > > Hi, > > I'm so happy to hear from you. > How about late September after thanksgiving? > > Best regards, > > Hwansung > > > 2019년 8월 27일 (화) 오후 9:05, Woonsan Ko 님이 작성: > > > Hi, > > > > I'm going to stay in South Korea in Sept. and Oct. If anyone is > > willing to meet and chat (perhaps over beer), let me know. I'd be very > > happy. ;-) > > > > Kind regards, > > > > Woonsan > >
Meet and chat in Seoul area?
Hi, I'm going to stay in South Korea in Sept. and Oct. If anyone is willing to meet and chat (perhaps over beer), let me know. I'd be very happy. ;-) Kind regards, Woonsan
Re: Podling Report Reminder - August 2019
Hi Do Yung, Could you update the wiki page as well? - https://cwiki.apache.org/confluence/display/INCUBATOR/August2019 Regards, Woonsan On Wed, Aug 7, 2019 at 9:35 AM Woonsan Ko wrote: > > Thanks, Do Yung! > I think it captures our status very well. > > Regards, > > Woonsan > > On Wed, Aug 7, 2019 at 8:39 AM DO YUNG YOON wrote: > > > > Hi > > > > Here is my draft for the report. Apologies for being late. Please review > > this. > > > > S2Graph > > > > S2Graph is a distributed and scalable OLTP graph database built on Apache > > HBase to support fast traversal of extremely large graphs. > > > > S2Graph has been incubating since 2015-11-29. > > > > Three most important issues to address in the move towards graduation: > > > > 1. Make the third release. > > 2. Attract more users and contributors. > > 3. Build the developer community in both size and diversity. > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > > of? > > > > None > > > > How has the community developed since the last report? > > > > * There were some questions and answers from the community about how to > > getting started. > > * New feature requests are opened on JIRA. > > > > How has the project developed since the last report? > > > > * Providing OpenAPI documentation for REST API is pending since there was > > lack of discussion. > > * It has been very quiet since the last report(only 1 JIRA issue opened). > > > > How would you assess the podling's maturity? > > Please feel free to add your own commentary. > > > > [ ] Initial setup > > [ ] Working towards first release > > [X] Community building > > [ ] Nearing graduation > > [ ] Other: > > > > Date of last release: > > > > 2017-08-26 > > > > When were the last committers or PPMC members elected? > > > > Have your mentors been helpful and responsive or are things falling > > through the cracks? In the latter case, please list any open issues > > that need to be addressed. > > > > * Our mentor is very helpful and responsive. > > > > Signed-off-by: > > > > > > On Wed, Aug 7, 2019 at 12:05 PM Justin Mclean wrote: > > > > > Hi, > > > > > > Just a friendly reminder that the report is due in a day. Is anyone > > > working on it? > > > > > > Thanks, > > > Justin > > >
Re: Podling Report Reminder - August 2019
Thanks, Do Yung! I think it captures our status very well. Regards, Woonsan On Wed, Aug 7, 2019 at 8:39 AM DO YUNG YOON wrote: > > Hi > > Here is my draft for the report. Apologies for being late. Please review > this. > > S2Graph > > S2Graph is a distributed and scalable OLTP graph database built on Apache > HBase to support fast traversal of extremely large graphs. > > S2Graph has been incubating since 2015-11-29. > > Three most important issues to address in the move towards graduation: > > 1. Make the third release. > 2. Attract more users and contributors. > 3. Build the developer community in both size and diversity. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > None > > How has the community developed since the last report? > > * There were some questions and answers from the community about how to > getting started. > * New feature requests are opened on JIRA. > > How has the project developed since the last report? > > * Providing OpenAPI documentation for REST API is pending since there was > lack of discussion. > * It has been very quiet since the last report(only 1 JIRA issue opened). > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] Initial setup > [ ] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > 2017-08-26 > > When were the last committers or PPMC members elected? > > Have your mentors been helpful and responsive or are things falling > through the cracks? In the latter case, please list any open issues > that need to be addressed. > > * Our mentor is very helpful and responsive. > > Signed-off-by: > > > On Wed, Aug 7, 2019 at 12:05 PM Justin Mclean wrote: > > > Hi, > > > > Just a friendly reminder that the report is due in a day. Is anyone > > working on it? > > > > Thanks, > > Justin > >
Fwd: Podling Report Reminder - August 2019
Hi S2Graph devs, I think you have already seen this reminder. The report submission is due on August 7th. Could you prepare a draft and ask others to review the draft for enough time before submission this time? Kind regards, Woonsan -- Forwarded message - From: Date: Wed, Jul 24, 2019 at 12:41 AM Subject: Podling Report Reminder - August 2019 To: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 August 2019, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, August 07). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/August2019 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Swagger Doc and UI support (Was: Documentation to the official online site svn?)
Hi Do Yung,
I see your point. Native support in Scala + Akka is better than manual
edits, of course.
There seems to be many more different libraries at the moment in Scala
ecosystem than Java's, like this one too:
- https://github.com/swagger-akka-http/swagger-akka-http
I'm not yet experienced much in Scala web application framework world,
so I can't really judge them. ;-) So, I'm open to you guys' opinions
and preferences.
What do others think?
Regards,
Woonsan
On Wed, May 1, 2019 at 4:31 AM DO YUNG YOON wrote:
>
> Hi Woonsan.
>
> Sorry for the late response. It took me for a while to figure out what
> would be a nice way for working with OpenAPI document spec.
>
> I agree with your two cents, especially the importance of generating rest
> API reference through the right tool.
>
> Here is the tools I played with a little bit.
>
> - tapir: https://github.com/softwaremill/tapir
> - endpoints: http://julienrf.github.io/endpoints/index.html
>
> Personally, I prefer tapir, but it seems like it does not provide scala
> 2.11 available on maven central. I spent few days to upgrade scala version
> from 2.11 to 2.12, but realize it is not that easy(we may need to open up a
> separate discussion how we are going to upgrade scala version to 2.12).
>
> so just played with endpoints at this point and just sharing it with you to
> check if we are doing the right thing.
>
> here is how to test this PR(
> https://github.com/woonsan/incubator-s2graph/pull/1)
>
> 1. setup docker image on local for hbase.
>
> cd dev_support; docker-compose up graph_hbase
>
> 2. run akka http server in dev environment.
>
> sbt 'project s2http' '~reStart'
>
> 3. check the specs that generated by documentation server/spec.
>
> http://localhost:8000/api-docs/documentation.json
>
> 4. check the AdminEndpoints
>
> this is where our admin specs will reside on.
> I added few more specs for listing service/label/serviceColumns etc to
> validate if they are working.
>
> ex)
> - localhost:8000/admin/listServices
> - localhost:8000/admin/listLabels
> - localhost:8000/admin/listServiceColumns/s2graph
>
> IMAO, The nice thing about the above two libraries is that it separates the
> implementation and spec but still validate it on compile time, which I
> prefer over the annotation approach.
> I think it takes some time to get used to it for the first time, then after
> struggling, the library shine and basically, help us to synchronize API and
> doc so worth it.
>
> Please review and give any comments.
>
> On Wed, Apr 10, 2019 at 8:24 AM Woonsan Ko wrote:
>
> > On Mon, Apr 8, 2019 at 6:58 PM Woonsan Ko wrote:
> > >
> > > Hi Daewon, Do Yung and/or anyone interested in,
> > >
> > > I've just submitted a PR which has the swagger UI support with the
> > > default swagger document, initially for admin services:
> > > - https://github.com/apache/incubator-s2graph/pull/197
> > >
> > > I think Swagger UI with the default swagger doc for the APIs will make
> > > it easier for many devs.
> > > Could you please review it?
> > >
> > > I figured out how to add /api-docs route there, but feel free to
> > > correct it if I didn't follow any (Scala or Akka) best practices. ;-)
> > >
> > > As described in the PR description, the following operations work fine
> > > with the examples:
> > > - /admin/createService, /admin/createLabel, /admin/addIndex,
> > > /admin/getLabel/{name}
> > >
> > > But, the following returns 404, for some reason which I can't figure out
> > now:
> > > - /admin/deleteLabel/{name}, /admin/addProp/{name},
> > /admin/createServiceColumn
> >
> > I've pushed more and now those three are working fine.
> > I've noticed that `/admin/deleteLabel/{name}` in documentation was
> > changed to `/admin/deleteLabelReally/{name}` in code:
> > -
> > https://github.com/apache/incubator-s2graph/blob/master/s2http/src/main/scala/org/apache/s2graph/http/S2GraphAdminRoute.scala#L226
> >
> > There seems to be many in code outdating the documentation. For
> > example, there are many undocumented operations too. e.g. renameLabel,
> > copyLabel, swapLabel, etc.
> >
> > My two cents:
> > If you folks like the OpenAPI (swagger) document and its UI, then I'd
> > like to suggest you should keep the swagger doc as the single source
> > of truth for internal/external developers who are using the APIs,
> > always keeping it synchronized with the code. So, for example, if
> > someone makes changes in the REST APIs, it must be affected in the
> > OpenAPI (swagger) doc, too.
> > And,
Re: It's time to report! (Was: Podling report due)
It looks good to me. Would you also update the wiki page? Then I can sign it off. Thanks, Woonsan On Wed, May 1, 2019 at 4:17 AM DO YUNG YOON wrote: > > Hi all. > > I just prepared the first version of the draft. Please review and let me > know what you think > > > S2Graph > > S2Graph is a distributed and scalable OLTP graph database built on Apache > HBase to support fast traversal of extremely large graphs. > > S2Graph has been incubating since 2015-11-29. > > Three most important issues to address in the move towards graduation: > > 1. Make the third release. > 2. Attract more users and contributors. > 3. Build the developer community in both size and diversity. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > None > > How has the community developed since the last report? > > * There were some discussions on the documentation of the project. > * There were some questions and answers from the community about the > migration tool > > How has the project developed since the last report? > > * Working on providing OpenAPI documentation for REST API. > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] Initial setup > [ ] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > 2017-08-26 > > When were the last committers or PPMC members elected? > > Have your mentors been helpful and responsive or are things falling > through the cracks? In the latter case, please list any open issues > that need to be addressed. > > * Our mentor is very helpful and responsive. > > Signed-off-by: > > > On Wed, May 1, 2019 at 10:19 AM Woonsan Ko wrote: > > > Hi S2Graphe PPMC, > > > > Today May 1st is the expected due date to submit your podling project > > report. > > > > Just to repeat what Justin encouraged you folks several times already, > > - PPMC needs to submit the report until May 1st, in order to give all > > PPMC members and mentors enough time to review and discuss. > > - And all the PPMC reports are gathered and reviewed again by IPMC to > > submit to the board finally a week prior (May 8th) to the board > > meeting (on May 15th). > > > > Report submission (~May 1st) -> PPMC/Mentors/IPMC review (~May 8th) -> > > Board meeting (May 15th). > > > > If we delay it, IPMC won't have enough time to review and assess the > > status. > > > > So, could you draft and submit the report as soon as possible? > > Also, I encourage all PPMC members to review the report and discuss > > things if necessary. > > > > Kind regards, > > > > Woonsan > > > > -- Forwarded message - > > From: Justin Mclean > > Date: Tue, Apr 30, 2019 at 8:44 PM > > Subject: Podling report due > > To: > > > > > > Hi, > > > > Given the report date falls on the 1st this month we’re going to give > > codlings a couple of days (until Friday) to get them in. > > > > The report can be found here: > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2019 > > > > We still have the following reports to be filled in: > > ECharts > > Edgent > > Milagro > > S2Graph > > SDAP > > Tamaya > > Toree > > Training > > Tuweni > > > > I can see that Training is working on a a report. > > > > Thanks, > > Justin > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > >
It's time to report! (Was: Podling report due)
Hi S2Graphe PPMC, Today May 1st is the expected due date to submit your podling project report. Just to repeat what Justin encouraged you folks several times already, - PPMC needs to submit the report until May 1st, in order to give all PPMC members and mentors enough time to review and discuss. - And all the PPMC reports are gathered and reviewed again by IPMC to submit to the board finally a week prior (May 8th) to the board meeting (on May 15th). Report submission (~May 1st) -> PPMC/Mentors/IPMC review (~May 8th) -> Board meeting (May 15th). If we delay it, IPMC won't have enough time to review and assess the status. So, could you draft and submit the report as soon as possible? Also, I encourage all PPMC members to review the report and discuss things if necessary. Kind regards, Woonsan -- Forwarded message - From: Justin Mclean Date: Tue, Apr 30, 2019 at 8:44 PM Subject: Podling report due To: Hi, Given the report date falls on the 1st this month we’re going to give codlings a couple of days (until Friday) to get them in. The report can be found here: https://cwiki.apache.org/confluence/display/INCUBATOR/May2019 We still have the following reports to be filled in: ECharts Edgent Milagro S2Graph SDAP Tamaya Toree Training Tuweni I can see that Training is working on a a report. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Swagger Doc and UI support (Was: Documentation to the official online site svn?)
Cool! Thank you sir!
Woonsan
On Tue, Apr 9, 2019 at 8:48 AM DO YUNG YOON wrote:
>
> Hi Woonsan. Sorry for the late reply.
>
> I really appreciate getting involved and I would love to review it.
> I will read through the PR on this week, then ask any questions on this
> thread.
>
> Thanks for your contribution!
>
> On Tue, Apr 9, 2019 at 7:58 AM Woonsan Ko wrote:
>
> > Hi Daewon, Do Yung and/or anyone interested in,
> >
> > I've just submitted a PR which has the swagger UI support with the
> > default swagger document, initially for admin services:
> > - https://github.com/apache/incubator-s2graph/pull/197
> >
> > I think Swagger UI with the default swagger doc for the APIs will make
> > it easier for many devs.
> > Could you please review it?
> >
> > I figured out how to add /api-docs route there, but feel free to
> > correct it if I didn't follow any (Scala or Akka) best practices. ;-)
> >
> > As described in the PR description, the following operations work fine
> > with the examples:
> > - /admin/createService, /admin/createLabel, /admin/addIndex,
> > /admin/getLabel/{name}
> >
> > But, the following returns 404, for some reason which I can't figure out
> > now:
> > - /admin/deleteLabel/{name}, /admin/addProp/{name},
> > /admin/createServiceColumn
> >
> > Kind regards,
> >
> > Woonsan
> >
> > On Thu, Mar 28, 2019 at 9:45 AM Woonsan Ko wrote:
> > >
> > > On Thu, Mar 28, 2019 at 9:19 AM DO YUNG YOON wrote:
> > > >
> > > > +1 for 'running' examples and would be happy to help if there is
> > anything I
> > > > can help with.
> > > >
> > > > Also while I was going through the documentation to check if it is
> > correct,
> > > > I found it is a bit tedious to copy payload on the doc to rest
> > client(such
> > > > as postman).
> > > > I wish there was a documentation tool integration, such as swagger,
> > which
> > > > also provides specs and UI to try each endpoint with examples.
> > > > I think integration with documentation tools is good for not only for
> > users
> > > > but also developers who set up local development environments and fix
> > code
> > > > and testing.
> > > >
> > > > Any thoughts?
> > >
> > > +1
> > > Great idea!
> > > If we provide a swagger UI (e.g, http://localhost:8000/api-docs), it
> > > will really boost developers understanding!
> > > We can probably include swagger UI under the /api-docs endpoint with a
> > > swagger.{json|yaml} file. I'm not accustomed to the scala web
> > > framework, but if someone expose a simple index.html under the
> > > /api-docs, then I can contribute or help create a pull request to
> > > enable swagger UI.
> > >
> > > Cheers,
> > >
> > > Woonsan
> > >
> > > >
> > > >
> > > > On Thu, Mar 28, 2019 at 10:05 PM Woonsan Ko
> > wrote:
> > > >
> > > > > Wow, this is great!!!
> > > > > Thank you very much.
> > > > >
> > > > > As a side note, I'll try to follow the documentation to implement
> > > > > something simple -- by using S2Graph of course -- such as "Related
> > > > > articles" or "Related products" which are really popular use cases in
> > > > > most websites nowadays, but it's hard to implement actually in an
> > > > > automated way based on users' behaviors.
> > > > > If we have simple 'running' examples somewhere for normal web
> > > > > developers, I think it would help people adopt this project and
> > > > > solutions.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Woonsan
> > > > >
> > > > > On Thu, Mar 28, 2019 at 8:02 AM DO YUNG YOON
> > wrote:
> > > > > >
> > > > > > Hi Woonsan, Sorry for being late.
> > > > > >
> > > > > > I followed the instructions and the changes are now pushed to svn.
> > > > > >
> > > > > > Here is the updates
> > > > > >
> > > > > > - svn: https://svn.apache.org/repos/asf/incubator/s2graph/site
> > (revision
> > > > > > 1856470)
> > > > > > - doc link on incubator site: *
> > > > > https://s2graph.apache.org
Swagger Doc and UI support (Was: Documentation to the official online site svn?)
Hi Daewon, Do Yung and/or anyone interested in,
I've just submitted a PR which has the swagger UI support with the
default swagger document, initially for admin services:
- https://github.com/apache/incubator-s2graph/pull/197
I think Swagger UI with the default swagger doc for the APIs will make
it easier for many devs.
Could you please review it?
I figured out how to add /api-docs route there, but feel free to
correct it if I didn't follow any (Scala or Akka) best practices. ;-)
As described in the PR description, the following operations work fine
with the examples:
- /admin/createService, /admin/createLabel, /admin/addIndex,
/admin/getLabel/{name}
But, the following returns 404, for some reason which I can't figure out now:
- /admin/deleteLabel/{name}, /admin/addProp/{name}, /admin/createServiceColumn
Kind regards,
Woonsan
On Thu, Mar 28, 2019 at 9:45 AM Woonsan Ko wrote:
>
> On Thu, Mar 28, 2019 at 9:19 AM DO YUNG YOON wrote:
> >
> > +1 for 'running' examples and would be happy to help if there is anything I
> > can help with.
> >
> > Also while I was going through the documentation to check if it is correct,
> > I found it is a bit tedious to copy payload on the doc to rest client(such
> > as postman).
> > I wish there was a documentation tool integration, such as swagger, which
> > also provides specs and UI to try each endpoint with examples.
> > I think integration with documentation tools is good for not only for users
> > but also developers who set up local development environments and fix code
> > and testing.
> >
> > Any thoughts?
>
> +1
> Great idea!
> If we provide a swagger UI (e.g, http://localhost:8000/api-docs), it
> will really boost developers understanding!
> We can probably include swagger UI under the /api-docs endpoint with a
> swagger.{json|yaml} file. I'm not accustomed to the scala web
> framework, but if someone expose a simple index.html under the
> /api-docs, then I can contribute or help create a pull request to
> enable swagger UI.
>
> Cheers,
>
> Woonsan
>
> >
> >
> > On Thu, Mar 28, 2019 at 10:05 PM Woonsan Ko wrote:
> >
> > > Wow, this is great!!!
> > > Thank you very much.
> > >
> > > As a side note, I'll try to follow the documentation to implement
> > > something simple -- by using S2Graph of course -- such as "Related
> > > articles" or "Related products" which are really popular use cases in
> > > most websites nowadays, but it's hard to implement actually in an
> > > automated way based on users' behaviors.
> > > If we have simple 'running' examples somewhere for normal web
> > > developers, I think it would help people adopt this project and
> > > solutions.
> > >
> > > Cheers,
> > >
> > > Woonsan
> > >
> > > On Thu, Mar 28, 2019 at 8:02 AM DO YUNG YOON wrote:
> > > >
> > > > Hi Woonsan, Sorry for being late.
> > > >
> > > > I followed the instructions and the changes are now pushed to svn.
> > > >
> > > > Here is the updates
> > > >
> > > > - svn: https://svn.apache.org/repos/asf/incubator/s2graph/site (revision
> > > > 1856470)
> > > > - doc link on incubator site: *
> > > https://s2graph.apache.org/docs/index.html
> > > > <https://s2graph.apache.org/docs/index.html>*
> > > >
> > > > Please check the updates and feel free to comment
> > > >
> > > >
> > > > On Tue, Mar 5, 2019 at 11:10 PM Woonsan Ko wrote:
> > > >
> > > > > Thanks a lot, Do Yung, as always!
> > > > > Please tell me if there's anything I can help with.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Woonsan
> > > > >
> > > > > On Tue, Mar 5, 2019 at 12:12 AM DO YUNG YOON wrote:
> > > > > >
> > > > > > Hi Woonsan.
> > > > > >
> > > > > > I agree with your suggestion, and I am volunteering for this.
> > > > > > Let me try working on this on weekends then I will share any
> > > > > > questions/updates.
> > > > > >
> > > > > > Thanks for your suggestion.
> > > > > >
> > > > > >
> > > > > > On Tue, Mar 5, 2019 at 11:27 AM Woonsan Ko
> > > wrote:
> > > > > >
> > > > > > > Hi folks,
> > > > > > >
> > > > > > > At the moment, the "Docs" l
[jira] [Commented] (S2GRAPH-253) Swagger UI provision for HTTP API
[
https://issues.apache.org/jira/browse/S2GRAPH-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811984#comment-16811984
]
Woonsan Ko commented on S2GRAPH-253:
Hopefully I'd like to submit a pull request for this improvement from here:
- https://github.com/woonsan/incubator-s2graph/tree/feature/S2GRAPH-253
> Swagger UI provision for HTTP API
> -
>
> Key: S2GRAPH-253
> URL: https://issues.apache.org/jira/browse/S2GRAPH-253
> Project: S2Graph
> Issue Type: New Feature
> Reporter: Woonsan Ko
>Priority: Major
>
> It would be nice if the default swagger UI is provided through
> {{http://localhost:8080/api-docs}} by default for the HTTP APIs:
> - http://s2graph.incubator.apache.org/docs/api/index.html
> It would help people follow the examples in the documentation a lot easier
> than using curl commands.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (S2GRAPH-253) Swagger UI provision for HTTP API
Woonsan Ko created S2GRAPH-253:
--
Summary: Swagger UI provision for HTTP API
Key: S2GRAPH-253
URL: https://issues.apache.org/jira/browse/S2GRAPH-253
Project: S2Graph
Issue Type: New Feature
Reporter: Woonsan Ko
It would be nice if the default swagger UI is provided through
{{http://localhost:8080/api-docs}} by default for the HTTP APIs:
- http://s2graph.incubator.apache.org/docs/api/index.html
It would help people follow the examples in the documentation a lot easier than
using curl commands.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Call for Presentations open for ApacheCon NA and EU 2019!
Hi Graph processing devs! The Call for Presentations are now open in both events this year: - ApacheCon NA (in Las Vegas): https://apachecon.com/acna19/cfp.html - ApacheCon EU (in Berlin): https://aceu19.apachecon.com/call-presentations (The second one is being redirected to the first one at the moment. Perhaps they accept all together or they will change it later...) In the topics, you will see "Graph processing" topic category! I believe you guys and some others in TinkerPop project will be best suited for the topic! Please have an interest in both events, and submit your presentations! ;-) It is a great chance to visit Las Vegas and enjoy Oktoberfest in Berlin! By the way, I personally think it would be great if the presentations show how easy, how useful and how beneficial it is to apply your technologies in real projects. Most people want to hear about some good stuffs they can try now in their projects, from confident 'sellers' (in other words, don't need to talk about any doubts out there in the short time before they ask, but just say it is the best choice with certainty from your experience, like you explain it to your internal colleagues, which is my $0.02). ;-) Anyway, I hope you guys rock in this autumn! Cheers, Woonsan
Re: Documentation to the official online site svn?
Wow, this is great!!! Thank you very much. As a side note, I'll try to follow the documentation to implement something simple -- by using S2Graph of course -- such as "Related articles" or "Related products" which are really popular use cases in most websites nowadays, but it's hard to implement actually in an automated way based on users' behaviors. If we have simple 'running' examples somewhere for normal web developers, I think it would help people adopt this project and solutions. Cheers, Woonsan On Thu, Mar 28, 2019 at 8:02 AM DO YUNG YOON wrote: > > Hi Woonsan, Sorry for being late. > > I followed the instructions and the changes are now pushed to svn. > > Here is the updates > > - svn: https://svn.apache.org/repos/asf/incubator/s2graph/site (revision > 1856470) > - doc link on incubator site: *https://s2graph.apache.org/docs/index.html > <https://s2graph.apache.org/docs/index.html>* > > Please check the updates and feel free to comment > > > On Tue, Mar 5, 2019 at 11:10 PM Woonsan Ko wrote: > > > Thanks a lot, Do Yung, as always! > > Please tell me if there's anything I can help with. > > > > Cheers, > > > > Woonsan > > > > On Tue, Mar 5, 2019 at 12:12 AM DO YUNG YOON wrote: > > > > > > Hi Woonsan. > > > > > > I agree with your suggestion, and I am volunteering for this. > > > Let me try working on this on weekends then I will share any > > > questions/updates. > > > > > > Thanks for your suggestion. > > > > > > > > > On Tue, Mar 5, 2019 at 11:27 AM Woonsan Ko wrote: > > > > > > > Hi folks, > > > > > > > > At the moment, the "Docs" link at the top menu bar [1] is linked to a > > > > non-ASF URL [2]. > > > > I don't think we can keep the non-ASF pages there in the future. > > > > Furthermore, the documentation there is outdated from the > > > > documentation source at doc/. > > > > > > > > Our official documentation repository is the SVN [3], as of [4]. > > > > > > > > Therefore, I'd like to propose the following: > > > > 1. Initially one of the committers should generate the site html from > > > > the doc/ in git source repo, following the instruction in > > > > doc/readme.md, until `make html`, which generates all the html and > > > > other static resource files at docs/build/html/. (I've just tested and > > > > it works fine.) > > > >And, the generated files at docs/build/html/** should be committed > > > > to a new directory, "docs", in [3]. > > > > 2. Change the "Docs" menu link to "docs/index.html" from the external > > link. > > > > 3. From now on, whenever committers update documentation, once in a > > > > while, do the step 1 and 2 periodically, to synchronize the online > > > > site with the documentation source. > > > > > > > > When we really want to expand the community during the incubation > > > > period, the online documentation is really crucial: new comers start > > > > from there... > > > > > > > > Any thoughts? > > > > If this sounds okay, any volunteers? > > > > > > > > Regards, > > > > > > > > Woonsan > > > > > > > > [1] http://s2graph.incubator.apache.org/ > > > > [2] https://steamshon.gitbooks.io/s2graph-book/content/ > > > > [3] http://svn.apache.org/repos/asf/incubator/s2graph/site/ > > > > [4] https://issues.apache.org/jira/browse/INFRA-11806 > > > > > >
Re: Documentation to the official online site svn?
Thanks a lot, Do Yung, as always! Please tell me if there's anything I can help with. Cheers, Woonsan On Tue, Mar 5, 2019 at 12:12 AM DO YUNG YOON wrote: > > Hi Woonsan. > > I agree with your suggestion, and I am volunteering for this. > Let me try working on this on weekends then I will share any > questions/updates. > > Thanks for your suggestion. > > > On Tue, Mar 5, 2019 at 11:27 AM Woonsan Ko wrote: > > > Hi folks, > > > > At the moment, the "Docs" link at the top menu bar [1] is linked to a > > non-ASF URL [2]. > > I don't think we can keep the non-ASF pages there in the future. > > Furthermore, the documentation there is outdated from the > > documentation source at doc/. > > > > Our official documentation repository is the SVN [3], as of [4]. > > > > Therefore, I'd like to propose the following: > > 1. Initially one of the committers should generate the site html from > > the doc/ in git source repo, following the instruction in > > doc/readme.md, until `make html`, which generates all the html and > > other static resource files at docs/build/html/. (I've just tested and > > it works fine.) > >And, the generated files at docs/build/html/** should be committed > > to a new directory, "docs", in [3]. > > 2. Change the "Docs" menu link to "docs/index.html" from the external link. > > 3. From now on, whenever committers update documentation, once in a > > while, do the step 1 and 2 periodically, to synchronize the online > > site with the documentation source. > > > > When we really want to expand the community during the incubation > > period, the online documentation is really crucial: new comers start > > from there... > > > > Any thoughts? > > If this sounds okay, any volunteers? > > > > Regards, > > > > Woonsan > > > > [1] http://s2graph.incubator.apache.org/ > > [2] https://steamshon.gitbooks.io/s2graph-book/content/ > > [3] http://svn.apache.org/repos/asf/incubator/s2graph/site/ > > [4] https://issues.apache.org/jira/browse/INFRA-11806 > >
Documentation to the official online site svn?
Hi folks, At the moment, the "Docs" link at the top menu bar [1] is linked to a non-ASF URL [2]. I don't think we can keep the non-ASF pages there in the future. Furthermore, the documentation there is outdated from the documentation source at doc/. Our official documentation repository is the SVN [3], as of [4]. Therefore, I'd like to propose the following: 1. Initially one of the committers should generate the site html from the doc/ in git source repo, following the instruction in doc/readme.md, until `make html`, which generates all the html and other static resource files at docs/build/html/. (I've just tested and it works fine.) And, the generated files at docs/build/html/** should be committed to a new directory, "docs", in [3]. 2. Change the "Docs" menu link to "docs/index.html" from the external link. 3. From now on, whenever committers update documentation, once in a while, do the step 1 and 2 periodically, to synchronize the online site with the documentation source. When we really want to expand the community during the incubation period, the online documentation is really crucial: new comers start from there... Any thoughts? If this sounds okay, any volunteers? Regards, Woonsan [1] http://s2graph.incubator.apache.org/ [2] https://steamshon.gitbooks.io/s2graph-book/content/ [3] http://svn.apache.org/repos/asf/incubator/s2graph/site/ [4] https://issues.apache.org/jira/browse/INFRA-11806
Re: Podling Report Reminder - February 2019
Hi Do Yung, Thanks for the draft and sharing it here. On Mon, Feb 4, 2019 at 6:41 PM DO YUNG YOON wrote: > > Hi folks. Here is the draft of Feb Report. > Please review and give feedback and I will update it on wiki tonight. > > > S2Graph > > S2Graph is a distributed and scalable OLTP graph database built on Apache > HBase to support fast traversal of extremely large graphs. > > S2Graph has been incubating since 2015-11-29. > > Three most important issues to address in the move towards graduation: > > 1. Make a third release. > 2. Attract more users and contributors. > 3. Build the developer community in both size and diversity. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware > of? > > None > > How has the community developed since the last report? > * Adding two committer. > * One more mentor has joined. > * There were some questions from the community about the deployment of > S2Graph. ... questions and answers ... ;-) > > How has the project developed since the last report? > > * We are overhauling documentation(S2GRAPH-246) > - Integrate gitbook into project. > * New HTTP interface integration(S2GRAPH-248) > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] Initial setup > [ ] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > 2017-08-26 > > When were the last committers or PPMC members elected? Could you add the dates and names for the new committers here? Find an example in the Tamaya podling report [1]. [1] https://wiki.apache.org/incubator/February2019 > > None Also, below this, could you add "Have your mentors been helpful and responsive ..." question and answer as well? See Tamaya as an example. The other things look good to me. Thanks, Woonsan > > Signed-off-by: > > [ ](s2graph) Andrew Purtell > Comments: > [ ](s2graph) Seetharam Venkatesh > Comments: > [ ](s2graph) Sergio Fernández > Comments: > [ ](s2graph) Woonsan Ko > Comments: > > On Sat, Jan 26, 2019 at 5:17 AM wrote: > > > Dear podling, > > > > This email was sent by an automated system on behalf of the Apache > > Incubator PMC. It is an initial reminder to give you plenty of time to > > prepare your quarterly board report. > > > > The board meeting is scheduled for Wed, 20 February 2019, 10:30 am PDT. > > The report for your podling will form a part of the Incubator PMC > > report. The Incubator PMC requires your report to be submitted 2 weeks > > before the board meeting, to allow sufficient time for review and > > submission (Wed, February 06). > > > > Please submit your report with sufficient time to allow the Incubator > > PMC, and subsequently board members to review and digest. Again, the > > very latest you should submit your report is 2 weeks prior to the board > > meeting. > > > > Candidate names should not be made public before people are actually > > elected, so please do not include the names of potential committers or > > PPMC members in your report. > > > > Thanks, > > > > The Apache Incubator PMC > > > > Submitting your Report > > > > -- > > > > Your report should contain the following: > > > > * Your project name > > * A brief description of your project, which assumes no knowledge of > > the project or necessarily of its field > > * A list of the three most important issues to address in the move > > towards graduation. > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > > aware of > > * How has the community developed since the last report > > * How has the project developed since the last report. > > * How does the podling rate their own maturity. > > > > This should be appended to the Incubator Wiki page at: > > > > https://wiki.apache.org/incubator/February2019 > > > > Note: This is manually populated. You may need to wait a little before > > this page is created from a template. > > > > Mentors > > --- > > > > Mentors should review reports for their project(s) and sign them off on > > the Incubator wiki page. Signing off reports shows that you are > > following the project - projects that are not signed may raise alarms > > for the Incubator PMC. > > > > Incubator PMC > >
Any volunteers to give answers? (Was: Deployment Architecture for s2Graph)
Hi S2Graph devs, Could anyone please give answer(s) to the user below? The answers don't have to be perfect, nor long, and the question could be too broad as well. Just giving some responses, possibly with links to any existing slides or documentation, or some comments and remarks from your experiences, will help grow the community. Keeping fair questions in the lists stale could give a wrong impressions to others. Keeping dialogues help. Thanks in advance, Woonsan -- Forwarded message - From: anuj kumar Date: Thu, Jan 17, 2019 at 8:48 PM Subject: Deployment Architecture for s2Graph To: Hi, I am planning to use S2 Graph for our graph use cases and wanted to know what is the preferred Deployment Architecture for the S2Graph ecosystem as a whole? Thanks, -- Anuj Kumar
Re: [NOTICE] Mandatory migration of git repos to gitbox.apache.org - three weeks left!
Hi S2Graph devs, Could someone volunteer to deal with gitbox migration explicitly? It is straightforward and pretty fast as mentioned below. Also, it will be more useful as you can take advantage of GitHub more natively. If you want to volunteer, you can simply start a voting proposing this move right now. Once a consensus made, you can create a INFRA ticket with a link to the voting result. Regards, Woonsan On Tue, Jan 15, 2019 at 4:50 PM Apache Infrastructure Team wrote: > > Hello, s2graph folks. > As stated earlier in 2018, and reiterated two weeks ago, all git > repositories must be migrated from the git-wip-us.apache.org URL to > gitbox.apache.org, as the old service is being decommissioned. Your > project is receiving this email because you still have repositories on > git-wip-us that needs to be migrated. > > The following repositories on git-wip-us belong to your project: > - incubator-s2graph.git > > > We are now entering the remaining three weeks of the mandated > (coordinated) move stage of the roadmap, and you are asked to please > coordinate migration with the Apache Infrastructure Team before February > 7th. All repositories not migrated on February 7th will be mass migrated > without warning, and we'd appreciate it if we could work together to > avoid a big mess that day :-). > > As stated earlier, moving to gitbox means you will get full write access > on GitHub as well, and be able to close/merge pull requests and much > more. The move is mandatory for all Apache projects using git. > > To have your repositories moved, please follow these steps: > > - Ensure consensus on the move (a link to a lists.apache.org thread will > suffice for us as evidence). > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA > > Your migration should only take a few minutes. If you wish to migrate > at a specific time of day or date, please do let us know in the ticket, > otherwise we will migrate at the earliest convenient time. > > There will be redirects in place from git-wip to gitbox, so requests > using the old remote origins should still work (however we encourage > people to update their remotes once migration has completed). > > As always, we appreciate your understanding and patience as we move > things around and work to provide better services and features for > the Apache Family. > > Should you wish to contact us with feedback or questions, please do so > at: us...@infra.apache.org. > > > With regards, > Apache Infrastructure >
Re: [DISCUSS]: asking about future of s2graph
On Mon, Dec 3, 2018 at 9:38 PM DO YUNG YOON wrote: > > Sorry for being late for reading this and Really Appreciate your opinion > Woonsan. > > > Write blogs with compelling stories for potential active users who need > to live on this technology, potentially with runnable GitHub project(s) for > readers Stories with real use cases attract people as their lives can rely > on those. It could make them active users at least. > > I would love to contribute to writing blogs, and runnable GitHub projects. > I tried few times to share the user stories from Kakao, but I think we are > open to any topics regarding S2Graph. Not sure how to start the blogs(I > guess we need to discuss what topics we cover), but count me in. Cool. I think we need more diverse stories telling how people can take advantage of the technology in their business, but at the same time it also needs more diverse people to contribute to the stories. Virtuous circle - that's what we need to make somehow perhaps at this point. I will also give more thoughts while learning this technology and we can later discuss it further... Anyway the more people writing more stories, the better making it happen. > > > Make more noise through Kakao, Twitter, Facebook, ... I have been a > non-social-web guy, but I have written blog articles for Apache Jackrabbit, > etc. JMeter twitts often to broadcast community activities. It works. > > I am not an active user on the social things so not sure how to working on > this. Maybe more social people can help us. we can try this when we have > some activities to broadcast such as release, adding the cool feature, > writing blogs so on. I see S2Graph has an official Twitter channel at least. Hasn't been updated since 2016 though. That could be a good start to revive. In FreeMarker project, we officially have a step to announce a release through its Twitter channel: - https://freemarker.apache.org/committer-howto.html#making-releases (See the step 22). By the way, do we have any meetups including S2Graph topics anywhere? In Seoul, for example? If we do, it's really valuable to announce those events through Twitter, etc. Meetups in local communities are really helpful to spread the great technologies and get to know potential active users/devs. Sometimes their creative questions from their work can also help our project. > > > If necessary or useful, consider writing those in Korean for local > communities, even in users@ mailing list. As long as you keep deciding > together in devs@, it's no problem. > > Actually, didn't know this. Would be helpful if we need to explain in > details for users who are not comfortable with English. Mixing up with the > first suggestion, I am wondering writing blogs in Korean is ok, since I > think it can help lowering the bar to local users. Yes. The only requirement in the ASF regarding languages is that devs need to use English in dev@ lists for transparent decision makings. In users@ list, StackOverflow, or any other user supporting channels, any language can be used. For example, if devs want to support users who ask questions in Korean, devs should feel free to respond in Korean. If devs need to take some insights (issues, improvement ideas, features, ...) from users@ to dev@ and discuss further, then they should start discussing in English with (brief) explanations from the insights. Then it's totally fine and it is more community-oriented practices, IMO. > > > Try to leverage your company's marketing department's power. They might > be eager to leverage you as an Apache community leaders for their reasons, > too. It could be a win-win. For example, I always try to secure my tech > session(s) about Apache Jackrabbit and related topics in my company's > annual conference, making deals with the marketing dept. > > Not sure if my company can support this, but worth to ask so let me ask > them. > > I hope we can further discuss how and what for blogs. All right. Thanks, Woonsan > > > On Thu, Nov 22, 2018 at 7:36 AM Woonsan Ko wrote: > > > Hi Do Yung, > > > > Thank you very much for the clear explanation. > > I've recently applied for a mentor for this project, so I'm reading past > > messages to understand the context now. ;-) > > Please see my comments inline. > > > > On 2018/10/31 06:56:15, DO YUNG YOON wrote: > > > It's been almost 3 years since s2graph has entered apache incubating. Our > > > community has not been successful to reach more people so far and I think > > > failing on growing community is the blocker issue for s2graph to > > graduate. > > > > > > I want to open up the discussion about what we have to do for growing > > > community, and eventually for graduation. > > > > > > In my
Re: I'd like to volunteer for mentoring S2Graph
Hi folks, Assuming no objection to my offer (perhaps quiet passion), I took the liberty to add my name to the S2Graph's mentors list in /incubator/public/trunk/content/podlings.xml. ;-) Thanks, Woonsan On Tue, Nov 20, 2018 at 7:33 PM Woonsan Ko wrote: > > Hi, > > I'd like to volunteer for a mentor for S2Graph project. > I think there's only one mentor remaining there, so I'd like to help > the community and project have a positive journey together and > represent themselves better. > I became a member this year and IPMC member recently. I am a PMC > member for Portals, FreeMarker and Jackrabbit as well. > > Kind regards, > > Woonsan
Re: [DISCUSS]: asking about future of s2graph
Hi Do Yung, Thank you very much for the clear explanation. I've recently applied for a mentor for this project, so I'm reading past messages to understand the context now. ;-) Please see my comments inline. On 2018/10/31 06:56:15, DO YUNG YOON wrote: > It's been almost 3 years since s2graph has entered apache incubating. Our > community has not been successful to reach more people so far and I think > failing on growing community is the blocker issue for s2graph to graduate. > > I want to open up the discussion about what we have to do for growing > community, and eventually for graduation. > > In my opinion, there are many parts have been changed after incubation. > > Followings are notable improvements we have been working on. > > 1. Query Interface > > - Tinkerpop OLTP support > - GraphQL support > > 2. Storage > > - Embedded RocksDB > - JDBC Storage > > 3. Full-text search > > - ElasticSearch for search on vertex/edge property > > 4. OLAP > > - S2GraphSource: dump HFile then creates Spark dataframe. > - S2GraphSink: sink Spark dataframe to S2Graph. > > Even though the project has been improved, our community has not been > grown. > > There could be many reasons that our community is not growing(please list > them so we can discuss if we can resolve them), but in my humble opinion, > we have not even released above improvements since the last release. > > As far as I remember, the last time we discuss the release was a long time > ago(2017-09-08) at here > https://lists.apache.org/thread.html/d0d8e264b7625128a6c2832723cf2ad555d169f9f277086ce69c3a7b@%3Cdev.s2graph.apache.org%3E > . > > Back then I was under pressure that we need to show that our community > growing after release, and since I was not sure, I avoid talking about the > release, and rather keep working on issues. > > Now I think it is much better to start by releasing it rather than only > just wondering how to grow the community. > > To grow the community, the very basic way I know is to keep improving the > project, releasing it, and advertise it, and get user feedback, and I think > we stuck to step 1 for too long time. My two cents: >From my experiences, it's really about selling your technology to people. We >might want to be focused on marketing a little bit more. Possible marketing >activities for community growth are in my mind: - Write blogs with compelling stories for potential active users who need to live on this technology, potentially with runnable GitHub project(s) for readers Stories with real use cases attract people as their lives can rely on those. It could make them active users at least. - Make more noise through Kakao, Twitter, Facebook, ... I have been a non-social-web guy, but I have written blog articles for Apache Jackrabbit, etc. JMeter twitts often to broadcast community activities. It works. - If necessary or useful, consider writing those in Korean for local communities, even in users@ mailing list. As long as you keep deciding together in devs@, it's no problem. - Try to leverage your company's marketing department's power. They might be eager to leverage you as an Apache community leaders for their reasons, too. It could be a win-win. For example, I always try to secure my tech session(s) about Apache Jackrabbit and related topics in my company's annual conference, making deals with the marketing dept. ;-) > > After a few more releases, then if there is no one found s2graph useful, > then I think we can happily retire from apache incubating, but I just don't > feel like we did our best yet. +1. I see many good things in this project with great potentials. > > I am willing to pursue building community, and I think it is worth to try > out a few more release until decide what's the next step. > > I want to ask what others think. are there any others who are willing to > get more involved? I'm learning now. I hope to get involved more soon. :-) Kind regards, Woonsan >
Re: HTTP interface integration and unfinished project (s2rest_netty) removal.
Now I see why it was broken. ;-) I recently re-subscribed the lists and started reading past messages to understand the context. I'm very looking forward to seeing the progress! Cheers, Woonsan On 2018/11/07 07:51:20, daewon wrote: > I've looked at the features that are available to remove the Play! > Framework. > > I have written my comments for each function groups. > > - The Admin and Create APIs have yet to integrate many functions into the > Play! controller code, so code separation must be preceded in order to move > functionality. > - The API with the `withWait` postfix of the Edge/Vertex creation API is an > API that tells the client whether the request is applied correctly. >This is a duplicate API that exists for backward compatibility. > - Management routes are suggested to unify API routes with prefixes such as > `/admin/?` or `/managment/?`. > - Server health_check or Counter related features are not available > anymore, so I suggest you exclude them. > > ## Edge creation > ### List of APIs to leave > POST/graphs/edges/insert > > POST/graphs/edges/insertBulk > POST/graphs/edges/delete > > POST/graphs/edges/deleteAll > > POST/graphs/edges/deleteAllWithOutWait > > POST/graphs/edges/update > > POST/graphs/edges/increment > POST/graphs/edges/incrementCount > POST/graphs/edges/bulk > > ### List of APIs that should be removed > POST/graphs/edges/deleteWithWait > > POST/graphs/edges/updateWithWait > > POST/graphs/edges/incrementWithWait > > POST/graphs/edges/bulkWithWait > > POST/graphs/edges/insertWithWait > > > ## Edge query > > ### List of APIs to leave > POST/graphs/getEdges > > POST/graphs/checkEdges > > > ### List of APIs that should be removed > POST/graphs/getEdgesGrouped > > POST/graphs/getEdgesGroupedExcluded > > POST/graphs/getEdgesGroupedExcludedFormatted > > GET /graphs/getEdge/:srcId/:tgtId/:labelName/:direction > > POST/graphs/getEdgesExcluded > > POST/graphs/getEdgesExcluded/grouped > > POST/graphs/getEdges/grouped > > > > ## Vertex related > ### List of APIs to leave > POST/graphs/getVertices > POST/graphs/vertices/insert > POST/graphs/vertices/delete > POST/graphs/vertices/deleteAll > > ### List of APIs that should be removed > POST/graphs/vertices/insert/:serviceName/:columnName > POST/graphs/vertices/delete/:serviceName/:columnName > > POST/graphs/vertices/deleteAll/:serviceName/:columnName > > POST/graphs/vertices/insertWithWait > > POST/graphs/vertices/deleteWithWait > > > ## Vertex related > ### List of APIs to leave > POST/graphs/createService > > GET /graphs/getService/:serviceName > > GET /graphs/getLabels/:serviceName > > POST/graphs/createLabel > > POST/graphs/addIndex > > GET /graphs/getLabel/:labelName > > PUT /graphs/deleteLabelReally/:labelName > > POST/graphs/addProp/:labelName > > POST/graphs/createServiceColumn > > PUT /graphs/deleteServiceColumn/:serviceName/:columnName > > POST/graphs/addServiceColumnProp/:serviceName/:columnName > > POST/graphs/addServiceColumnProps/:serviceName/:columnName > > GET /graphs/getServiceColumn/:serviceName/:columnName > > POST/graphs/createHTable > > GET /admin/labels/:serviceName > > POST/graphs/copyLabel/:oldLabelName/:newLabelName > > POST/graphs/renameLabel/:oldLabelName/:newLabelName > > POST/graphs/swapLabels/:leftLabelName/:rightLabelName > > POST/graphs/updateHTable/:labelName/:newHTableName > > PUT /graphs/loadCache > > > ## Experiment related > ### List of API to leave > POST/graphs/experiment/:accessToken/:experimentName/:uuid > > POST/graphs/experiments > > > ## publish (deprecated) > ### List of APIs that should be removed > POST/publish/:topic > > POST/publishOnly/:topic > > > Health Check(deprecated) > ### List of APIs that should be removed > GET /health_check.html > > PUT /health_check/:isHealthy > > > ## Counter related (deprecated) > ### List of APIs that should be removed > POST/counter/v1/:service/:action > GET /counter/v1/:service/:action > PUT /counter/v1/:service/:action > PUT /counter/v1/:service/:action/prepare > DELETE /counter/v1/:service/:action > GET /counter/v1/:service/:action/ranking > DELETE /counter/v1/:service/:action/ranking > GET
I'd like to volunteer for mentoring S2Graph
Hi, I'd like to volunteer for a mentor for S2Graph project. I think there's only one mentor remaining there, so I'd like to help the community and project have a positive journey together and represent themselves better. I became a member this year and IPMC member recently. I am a PMC member for Portals, FreeMarker and Jackrabbit as well. Kind regards, Woonsan
