Learning Objectives

• Learn LLM background technology

• Learn Javascript language and framework

• Learn basics of Front-end development

• Learn Cloud architecture and deployment

• Learn how to create high quality documentation

Expected Outcome and Deliverables

• An LLM prototype with acceptable time response and implementation costs

• A Front-end component prototype

• A simple container architecture

• A good quality documentation

Considerations to move to Incubated Project: Incubation entry considerations

Go to start of metadata

• Set up appointment with Marketing team to devise Name and Logo

• Set up chat channel named #{project-name} (see Create a Chat Channel)

• Set up mailing list named {project-name}@lists.hyperledger.org (see Create a Mailing List and Add Moderator and/or Owner to Mailing List)

• Set up Wiki space using project space (To be created in the meantime use the Sample Project Page as the home page in a blank space). Name the space projectname all lower case.
  
  • Label the page with project-home so that it shows up on the main page and project page automatically
  • Configure the sidebar on the space and remove the "Pages", "Blog", and "Space Shortcuts" sections by clicking on the `-` sign next to them until they appear as a `+` sign. Then save the changes.
  • Edit the Set Space Permissions for Anon to read only (and only view rights) to anonymous users.
• Add the Wiki space to the "Projects" menu (see Modify Top-Level Menu)
• Work with the project maintainers to determine how source control will be handled and what repositories are needed
• Set up Github repositories
  • Should have settings file; here's an example
  • Must comply with common repo structure (You have two quarters to comply, but it's easier to do up front)
    • Please note the repolinter section is in flux right now
• Make sure DCO is turned on
• Make sure Maintainers sign off on NEVER TURNING OFF DCO
• License Scan
• DCO Scan
• Is a security audit needed?
• Create an event on the TSC calendar for the first quarterly update (see example). We normally skip at least one quarter before requiring them to do their first update. That gives them time to get things up and running
• Create an event on the new working group's calendar to remind the subscribers that their TSC update is due (see example)
• Create a recurring event on the project's calendar for public calls
• Work with the marketing team to develop a project-specific webpage (see example)
• Work with the creative services team to create a project-specific logo (file Jira ticket similar to this example, minimum two weeks in advance)
• Work with pr@hyperledger.org to create a blog post (minimum two weeks in advance)
• Work with marketing@hyperledger.org on web assets:
  • Banner for homepage and greenhouse graphic tagline (if applicable)
  • Short description for Hyperledger projects landing page /projects
  • Extended description for dedicated project page
  • All currently available getting started resource pointers for the project page, i.e., Wiki, Github, WG, Chat, mailing list, video playlists 
• Add project maintainers to the maintainers list and send an introduction message welcoming them to the list
• Send out welcome email to the maintainers and invite them to an onboarding call and to the new maintainer orientation call
• Two months after welcome email is sent follow up with maintainers if they have not yet scheduled an onboarding call to see how things are going and if they need help
• Add to FAQ page
• Add to Video Checklist