Thanks for the pad, @liz. I added a little suggestion box for the community in the pad.

@warren Did you guys finally decide anything?

Hi, @ryzokuken -- have you had a chance to try writing some sample scripts, as I suggested above? Also, i think it's worthwhile to write out in more detail each step it'll take to implement the first couple bots, the ones you write the scripts for.

And potentially the steps to get a bot working on the PL website. What infrastructure will you need? A VM? Can you test it on Cloud9? How will a bot post a comment, or find comments? What API calls will you need plots2 to offer for reading recent posts, comments, or posting comments?

Thank you!

Hey @warren! I have indeed been working on the sample scripts, but the kind of request/response model the bot follows would totally depend if we're using ML+NLP or if we're hardcoding conversations. If you could tell me which one we'd proceed with, I could totally put up the scripts for reference (I would need to write them in code anyway).

Regarding the minor details, I guess it'll be more fruitful if we could discuss that in person, because:
A) I would be able to receive instant feedback and actually "discuss" rather than just stating my opinions.
B) This being a collaborative project, the opinions and doubts of everyone need to be addressed, rather than again, me stating my preferences and opinions.

Please feel free to drop me a mail or a comment in here regarding when you would be free to discuss this in the next couple of days 😄

Regarding the architecture, again, that's something we would need to discuss and that's exactly what I meant when I said that we need to make a design doc. Personally, I believe the best way for us to do this would be to host the bot on heroku for the time-being and trying to shift it to our own servers later in the future if we have the given resources (which are pretty minimal, tbh) and only if it promises a significant speed boost. (Which it will, if the majority of the bot activities would happen at publiclab.org rather than on Slack or Gitter or OFTC).

Hi, I'm happy to meet with you perhaps on Monday -- what times are you free? And as to the scripts, I think starting with a hard-coded one is a good place to begin, but I also think that posting one of each would help people understand the pros and cons of an NLP-based approach, by contrast to a hard-coded script. I'm not asking you necessarily to post a complete interaction as it'll be coded, but to illustrate a few initial options to help people understand what your bots could do, by example. Thanks!

On Monday, I would be free from around 4 PM in the evening to around 12 - 2 AM in the midnight. Considering you to be in the Eastern Standard Time timezone, I'd be free from 6:30 AM to 1:30-3:30 PM of your time. Thanks. Will be putting up a few sample scripts over here later today.

@warren Totally forgot that I have this week off as a holiday. Monday is the main festival (BTW, Happy Holi, everyone) but I'll try to stay online as much as I could. Ping me up whenever you're free. Could not work more on the scripts today because I had been working on the containerization. Hopefully, we would be able to provide a container-ed alternative to the usual development workflow and then automate almost every single bit of it by the end of this week (stay tuned :D)

@warren @liz @stevie Updated the note... Hope you guys find it up to the mark. There is some issue with the markdown being rendered, will look into it. Meanwhile, would you guys prefer me to put it elsewhere? Thanks

Ah this is super helpful, thank you @ryzokuken.

Hi, so on number 1, would that run in our chatroom, or where exactly? Do you have some ideas on one to run on submitted questions, for example? Maybe @stevie has thoughts on the kinds of helpful things a bot might ask someone for (like, if a photo is missing, or tags are missing, or something?)

Hi there, I'm also wondering about where it would live. I think a lot of first time PL users don't see or go to the chat, so I'm wondering if a bot on the dashboard might be more helpful if that's possible. I have a few ideas:

• I'm wondering if a bot could be used to help first time people who come with a specific interest, and direct them there more quickly. For example,

  • if someone comes with: "I just have a question". The bot could help get them to the Q/A interface and help them write a good question.
  • If someone wants to "share work" maybe the bot could help them find what subject they're interested in and direct them to: answering questions, updating a wiki, posting an activity on that topic.

• I think a bot might also be useful in helping people learn about what's on the dashboard and help them sort what material they want to see (the tab where you can select questions, research notes, comments and events).

• One other idea I'm thinking about is helping people who aren't coders post GitHub issues. I've started to see things that might be website/bug issues posted on the Q+A. A bot that could help people distinguish between the two and post accordingly might be really useful.

Also one question I have is how hard would it be to change what the bot does once it's made? My concern is, for example, if we have a bot that helps people navigate the dashboard, what happens if we change something on the dashboard?

Thanks for your work on this. It sounds really neat!!

Thanks for the feedback and appreciation, @warren and @stevie. I've thought over some of these issues, and would definitely love to discuss those. But commenting on this thread might not be our best option. Whenever you're free (if you're free at all) I would love to talk about these and any other issues you guys have in detail.

Hi, @ryzokuken -- I'm happy to meet tomorrow, but if you could try putting in some of your next questions here, it'll be easier for us to all stay in sync even if we can't all get on the same chat; of course, I'm happy to chat, and look forward to it tomorrow, but just thinking beyond the 1:1 discussion and how to get others' viewpoints in here.

Thanks!

Hi, @ryzokuken - saw your draft diagram on the chatroom and it's looking great -- left some comments there. Hope you're having a great weekend!

Updated the note with the flow of data diagram. Hope it helps in visualizing the flow of data to and from the bot. Please feel free to voice your concerns about the diagram and the bot in general.

@warren: Regarding your concerns with the diagram:
1. From User, here I mean the user interacting to the bot directly. Users would obviously interact to the bot through Github, but user actions on Github and Publiclab.org would seldom "trigger" some action on the bots' part. Atleast that's what I have in mind until now, although everything is subject to discussion and change.
2. Concerning which all actions would be required by the bot on each of these interfaces would depend highly on the use cases we put to work. The bot might or might not be required to post research notes, for instance. It would all depend on what the feature we're working on "requires" the bot to do.

Thanks

Ah, great, thank you! As to actions required, I think we might start with some simple ones, like:

• read listing of recent pull requests
• read pull requests
• read pull request comments
• comment on pull request
• all the above but for issues
• read listing of recent research notes
• read individual research notes
• read research note comments
• write research note comments

Not that we'd have to tackle all of these at once, but it'd be good to know how many distinct API URLs we're talking about. And for the Public Lab site, how many we'd have to create -- would this, for example, require making a unique Public Lab user account for the bot, and creating a unique token system so that it could post without needing to log in with a session?

Thanks!

@warren @stevie @liz Added the design guidelines. Please look into them and give feedback whenever your schedule permits.

@warren: I would look deeper into Github's API for these sample use cases (as they are pretty general use cases, I highly doubt that we would skip any of these in the original implementation). Meanwhile, let's see if the required functionality is available for the Publiclab API, and work on the calls that we need to make but which do not already exist.

Regarding the authentication part, isn't the API public, or does one need an Auth token (maybe something like OAuth tokens) in order to make requests? If so, then we would need to indeed make an Auth token for the bot and allow a sufficiently large number of calls (per day, if that's our metric) so that the bot functions properly. In that case, we would store our Auth key along with the other Auth keys (we would need OAuth tokens from Github, Gitter, Wikipedia, Google and any other services we use) in the environment file.

Otherwise, if the API is totally public without restrictions, I don't see why we would require an API key. An advantage of dropping the API key model (among a sea of disadvantages) that I would like to mention would be that a contributor would need to also register for API keys for all these services. Every single API key that we manage to cut down would slightly decrease the time and work required for setting up the project.

Thanks

Hi there! thanks for your work here. Probably because I don't know much about how programing works, I'm having a hard time understanding what you're asking for input on. Could you phrase your question or what you're looking for input on in a way a non-coder could better understand? If not, no worries but I know @warren is mostly away from internet for the next couple days, so we might need to wait until he has a moment to get back on and catch up.

Thanks again!

@stevie I would require input on the design side of things, as we would need the design to "just work" for everyone. I proposed a basic design concept (one that uses FABs and floating panes). I would love if you guys could propose ideas and make suggestions regarding the design as the current concept might not be the best we could do. Also, it would be super cool if we could somehow also involve people who are active users of the website to know what exactly they expect from us both feature-wise and design-wise. Thanks.

Hi, @ryzokuken - i was thinking of another idea for bots, tell me what you think:

A bot that:

• reads new questions
• finds most relevant keywords from title and body of questions (ones that are least generic)
• finds similar tags (possibly manipulating the keywords so that "photo" could also search for tags related to "camera" for example, or "spectrometer" for "spectral"... though starting with simple manipulations in the first version)
• asking if the asker has searched for these keywords, linking to them with [keyword](/tag/keyword)
• possibly displaying a grid of similar questions with an inline grid of them by tag, like: [questions:spectrometer]
• specifically helping them tag the question and notify people who've subscribed to answer questions on that topic, possibly either by adding the tag and re-triggering notifications, or by making the use of #tagname inline trigger notifications? We'd have to think about that.

All these interactions could happen in comments (and possibly answers if we find a very close match?).

Since this interaction could simply happen in the comments on a question, i think you could mock it up by editing an existing comment in your browser. Did you know you can use this javascript snippet in your console to make HTML content directly editable like rich text? window.document.body.contentEditable = true; -- You can even make a bookmark to the URL javascript:window.document.body.contentEditable = true; and use it. I find it very helpful for making mockups, because you can copy/paste HTML and type new content in, even copying things like buttons, for example. Maybe it'd help @stevie and me see a fully imagined script such as the ones you've outlined above, or the one I just suggested, using this technique, in a screenshot. What do you think?

Thanks for all your hard work on this!

Hi, @warren. Although what I had in mind was something like the Stack Overflow functionality that compares your question with questions that have already been answered by the community and redirect you to the appropriate answer instead, this indeed sounds like something we could do.

I guess we can also edit the contents of a webpage from the inspector pane inside the console? Will try to do that and post a screenshot soon.

@warren, I guess this is what you were talking about?

Hi @ryzokuken ! Great ideas and it really looks neat. But you also need to post the full proposal in the template provided along with the timeline. If you have already done that in your proposal in the GSoC website please update it here as well. Also it would be nice if you add this idea in the ideas list at https://publiclab.org/wiki/gsoc-ideas

@anayo2012 @jwarren I added a basic timeline, people provide feedback.

Updated the timeline please provide feedback as soon as possible if your schedule permits (we have an hour till the deadline).

Hi, @ryzokuken - just getting back in here now; just for starters, can you update the Cases above with a brief mention of

1. where the bot would appear (chatroom, comments, GitHub PR etc)
2. link to the "feed" or listing of where these show up, such as https://github.com/publiclab/plots2/pulls or https://chat.publiclab.org
3. what new APIs (if any) we'd need to read AND write to that feed?

This'll help us choose the very first, and understand some of the initial steps we'd have to take to do an initial test implementation. For example, i see you mention the JSON API in the first month, and the PublicLab.org microservice in the second. But I wasn't sure -- are you saying you'd set up a chatroom-based test case first to try things out, or do you think the PublicLab.org commenting API could be the initial test (since most community newcomers start there -- say, in a Question, and not in the chatroom).

I could see either being advantageous, because it'd be great to meet newcomers where they are first, but it could also be great to use the chatroom as a more flexible testing space before starting the extra integration with PublicLab.org and the challenge of working well with newcomers. What do you think, and @stevie and @ananyo2012, what are your thoughts?

Thanks!

It's a big project, and we'd like to identify smaller subsets to use as "pilot" exporatory initial projects that can be completed quickly so we can see how one possible implementation of the system works, then iterate/expand. I know it's tempting to build the whole architecture first, but if there is a narrower subset of the infrastructure we can build first, to better understand through a pilot bot, I think that'll be worthwhile. What do you think?

Hi there! I think starting out in the chatroom is a good idea!

@jywarren @stevie Updated the proposal with the external data that would be required and the location of each of the sample conversations. I would definitely love to move the interactions to multiple places closer to the actual work (eg: Questions and Github comments), but I think that chat is a more expressive and dynamic medium and it would be much easier to tinker with it (in the earlier phases of the bot atleast). Therefore, I would second @stevie and say that we should start out with the chatroom interface and add more interfaces later when the functionalities are better tested and more polished to avoid spamming both the Github repo and Publiclab website itself. (It is super easy to make a test chatroom and save everyone from the mess I would probably make while testing new features, and then push the more polished versions to the original chatroom + the github repo + the website)

The update looks super, and the chatroom-first plan too!